Positioning Rel-18

 RAN1#109-e

9.5       Study on expanded and improved NR positioning

Please refer to RP-213588 for detailed scope of the SI.

R1-2205574        Session notes for 9.5 (Study on expanded and improved NR positioning)       Ad-Hoc Chair (Huawei)

R1-2205226        Work Plan for Study Item on Expanded and Improved NR Positioning               Intel Corporation, CATT, Ericsson            (rev of R1-2204805)

R1-2204804         Draft skeleton of TR38.859             Intel Corporation

[109-e-R18-Pos-01] – Debdeep (Intel)

Email discussion and approval of TR skeleton for Rel-18 SI on expanded and improved NR positioning by May 13

R1-2205353        Draft skeleton of TR38.859           Rapporteur (Intel Corporation)

R1-2205358        FL summary on TR 38.859 skeleton for Rel-18 SI on expanded and improved NR positioning   Moderator (Intel Corporation)

Decision: As per email decision posted on May 16^th,

Agreement

·        TR skeleton in R1-2205398 for TR 38.859 for study on expanded and improved NR positioning is endorsed as v0.0.0.

R1-2205398        Draft skeleton of TR38.859           Rapporteur (Intel Corporation)

9.5.1        Sidelink positioning

9.5.1.1       SL positioning scenarios and requirements

Including specific target performance requirements

R1-2205194        Potential SL Positioning Scenarios and Requirements         Lenovo (rev of R1-2204557)

Proposal 1: RAN1 to select 1 or 2 representative commercial ranging use cases to derive commercial SL positioning requirements, preferably based on the KPIs, e.g., accuracy, latency aligned with that of V2X or Public Safety.

Proposal 2: Adopt a unified set of SL positioning requirements for all use cases as shown in Table 5 and for ease of evaluations, consider a common KPI target such as an absolute horizontal/vertical accuracy < 1m for 95% of UEs and a relative horizontal/vertical accuracy <1m for 95% of UEs.

Proposal 3: At least consider the following additional KPIs required SL Positioning use cases:

·        Direction/orientation accuracy

·        Concurrent UEs performing relative location estimation

·        Mobility parameters including velocity. FFS whether absolute and/or relative velocity is required.

Decision: The document is noted.

R1-2204309        Discussion on SL positioning scenarios and requirements   CMCC

Proposal 1: Select the following use cases for evaluation:

·        First priority: V2X use cases

·        Second priority: IIoT use cases

Proposal 2: Select set 2 defined in TR 38.845 as the target requirement for both V2X and IIoT use cases.

·        Set 2: 1 – 3 m with 95 – 99 % confidence level.

Proposal 3: Study and evaluate the following coverage scenarios:

·        First priority: in-coverage and out-of-coverage scenarios

·        Second priority: partial coverage scenarios

Proposal 4: Support of sidelink positioning operation in ITS and licensed band in FR1.

Decision: The document is noted.

R1-2204948        SL positioning scenarios and requirements             Ericsson

·        Proposal 1: Study the mechanisms to support in-coverage hybrid positioning (Uu+PC5)

·        Proposal 2: Public safety should be prioritized when selecting use cases and requirements for OoC

·        Proposal 3: Evaluations of positioning performance in partial coverage scenarios should not be performed.

·        Proposal 4: Target a small set of use cases for requirements and evaluations, that is, the ones presented in Table 1  and Table 2

Decision: The document is noted.

R1-2203057         Considerations on scenarios and target requirements for sidelink positioning               FUTUREWEI

R1-2203127         SL positioning scenarios and requirements   Nokia, Nokia Shanghai Bell

R1-2203162         Discussion on scenarios and requirements for sidelink positioning         Huawei, HiSilicon

R1-2203334         Consideration on SL positioning scenarios and requirements    Spreadtrum Communications

R1-2203465         Discussion on SL positioning scenarios and requirements         CATT, GOHIGH

R1-2203564         Discussion on SL positioning scenarios and requirements         vivo

R1-2203622         Discussion on scenarios and requirements for SL positioning   ZTE

R1-2203718         Discussion on SL positioning scenarios and requirements         LG Electronics

R1-2203737         Considerations on SL positioning scenarios and requirements  Sony

R1-2203751         Scenarios and requirements for sidelink positioning   MediaTek Inc.

R1-2203821         Discussion on sidelink positioning scenarios and requirement  xiaomi

R1-2203909         On SL Positioning Scenarios and Requirements          Samsung

R1-2203941         SL positioning scenarios and requirements   NEC

R1-2203978         Discussion on SL positioning scenarios and requirements         OPPO

R1-2204094         Discussion on V2X use cases, scenarios, and requirements for sidelink positioning               TOYOTA Info Technology Center

R1-2204130         Potential scenarios and requirements for SL positioning           InterDigital, Inc.

R1-2204251         Discussion on SL positioning scenarios and requirements         Apple

R1-2204666         Views on SL positioning scenarios and requirements Sharp

R1-2204753         Discussion on sidelink based positioning requirements & scenarios       CEWiT

R1-2204806         On SL positioning scenarios and requirements            Intel Corporation

R1-2204833         SL positioning scenarios and requirements   Fraunhofer IIS, Fraunhofer HHI

R1-2205036         Sidelink Positioning Scenarios and Requirements       Qualcomm Incorporated

[109-e-R18-Pos-02] – Debdeep (Intel)

Email discussion on SL positioning scenarios and requirements by May 20

-        Check points: May 16, May 20

Decision: As per email decision posted on May 16^th,

Agreement

Following two operation scenarios are considered for studies on SL positioning:

·        Scenario 1: PC5-only-based positioning

·        Scenario 2: Combination of Uu- and PC5-based positioning solutions

R1-2205177        FL summary #1 on SL positioning scenarios and requirements        Moderator (Intel)

From May 17^th GTW session

Agreement

For evaluations for SL positioning:

·        For V2X and public safety use-cases, at least in-coverage and out-of-coverage scenarios are considered.

·        For IIoT and commercial use-cases, at least in-coverage scenarios are considered.

Agreement

For the purpose of evaluations, in-coverage and out-of-coverage scenarios are prioritized during the SI.

·        Note: This prioritization is not intended to down-scope support of SL positioning for partial coverage scenarios.

Agreement

For evaluations for SL positioning:

·        Operation in FR1 with channel bandwidths of up to 100 MHz are considered.

·        Optional: Operation in FR2 with channel bandwidths of up to 400 MHz are considered.

Decision: As per email decision posted on May 19^th,

Agreement

Positioning accuracy requirements for SL positioning are expressed as accuracy requirements of particular percentiles of UEs for one or more of the following metrics:

·        Ranging accuracy, expressed as the difference (error) between the calculated distance/direction and the actual distance/direction in relation to another node

·        Relative positioning accuracy, expressed as the difference (error) between the calculated horizontal/vertical position and the actual horizontal/vertical position relative to another node

·        Absolute positioning accuracy. expressed the difference (error) between the calculated horizontal/vertical position and the actual horizontal/vertical position

·        Note: the exact applicability of particular requirements may vary across use-cases

Agreement

For evaluations of relative positioning, the horizontal plane is assumed parallel to the ground.

R1-2205527        FL summary #2 on SL positioning scenarios and requirements        Moderator (Intel)

From May 20^th GTW session

Working assumption

For evaluation of V2X use-cases for SL positioning, the following accuracy requirements are considered:

·        Set A (similar to “Set 2” defined in TR 38.845)

o   Horizontal accuracy of 1.5 m (absolute and relative); Vertical accuracy of 3 m (absolute and relative) for 90% of UEs

·        Set B (similar to “Set 3” defined in TR 38.845)

o   Horizontal accuracy of 0.5 m (absolute and relative); Vertical accuracy of 2 m (absolute and relative) for 90% of UEs

·        Note 1: For evaluated SL positioning methods, companies are expected to report:

o   whether each of the two requirements are satisfied, and

o   %-ile of UEs satisfying the target positioning accuracy for a requirement that may not be satisfied with 90%.

·        Note 2: target positioning requirements may not necessarily be reached for all scenarios and deployments

·        Note 3: all positioning techniques may not achieve all positioning requirements in all scenarios

Agreement

For evaluation of public safety use-cases for SL positioning solutions, the following accuracy requirements are considered:

·        1 m (absolute or relative) horizontal accuracy and 2 m (absolute or relative between 2 UEs) or 0.3 m (relative positioning change for one UE) vertical accuracy for 90% of UEs

·        Relative speed: up to 30 km/hr.

·        Note 1: For evaluated SL positioning methods, companies are expected to report:

o   whether the requirement is satisfied, and

o   %-ile of UEs satisfying the target positioning accuracy if the requirement may not be satisfied with 90%.

·        Note 2: target positioning requirements may not necessarily be reached for all scenarios and deployments

·        Note 3: all positioning techniques may not achieve all positioning requirements in all scenarios

Agreement

For evaluation of commercial use-cases for SL positioning solutions, the following accuracy requirements are considered:

·        1 m (absolute or relative) horizontal accuracy and 2 m (absolute or relative) vertical accuracy for 90% of UEs

·        Relative speed: up to 30 km/hr.

·        Note 1: For evaluated SL positioning methods, companies are expected to report:

o   whether the requirement is satisfied, and

o   %-ile of UEs satisfying the target positioning accuracy if the requirement may not be satisfied with 90%.

·        Note 2: target positioning requirements may not necessarily be reached for all scenarios and deployments

·        Note 3: all positioning techniques may not achieve all positioning requirements in all scenarios

Working assumption

For evaluation of IIoT use-cases for SL positioning solutions, the following accuracy requirements are considered:

·        For horizontal accuracy,

o   Set A: 1 m (absolute or relative) for 90% of UEs

o   Set B: 0.2 m (absolute or relative) for 90% of UEs

·        For vertical accuracy,

o   Set A: 1 m (absolute or relative) for 90% of UEs

o   Set B: 0.2 m (absolute or relative) for 90% of UEs

·        Relative speed: up to 30 km/hr.

·        Note 1: For evaluated SL positioning methods, companies are expected to report:

o   whether each of the two requirements are satisfied, and

o   %-ile of UEs satisfying the target positioning accuracy for a requirement that may not be satisfied with 90%.

·        Note 2: target positioning requirements may not necessarily be reached for all scenarios and deployments

·        Note 3: all positioning techniques may not achieve all positioning requirements in all scenarios

Decision: As per email decision posted on May 21^st,

Agreement

For evaluations in Rel-18, ranging requirements for SL positioning are defined as:

·        For a given use-case, the value of the distance requirement for ranging distance accuracy is same as the value identified for horizontal positioning accuracy for relative positioning.

·        The requirement on ranging direction accuracy is Y degrees for 90% of UEs.

o   FFS: Exact definition of ranging direction accuracy, including value(s) of Y and reference direction

Agreement

For Rel-18 studies on SL positioning, focus on positioning accuracy

·        Note: End-to-end positioning latency is expected to satisfy a latency budget of X second(s).

o   FFS: value of X

Final summary in R1-2205595.

9.5.1.2       Evaluation of SL positioning

Including evaluation methodology and performance evaluation results

R1-2204754        Discussion on evaluation methods and results of sidelink based positioning               CEWiT

·        Proposal 1: Rel 17 sidelink-based positioning evaluation should be performed for V2X, IIoT Public safety use cases for in coverage, partial coverage, and out of coverage scenarios.

·        Proposal 2: For Rel 17 sidelink evaluation, the simulation parameters form 38.855 and 38.857 for public safety and IIoT use cases can be reused.

·        Proposal 3: For Rel 17 sidelink evaluation, use simulation parameters from table 5 for V2X use cases.

·        Proposal 4: For uniform results, fix the UE dropping density per scenario that should be specified in the simulation assumptions.

Decision: The document is noted.

R1-2205186        Discussion on Evaluation for SL Positioning           Samsung              (rev of R1-2203910)

·        Proposal 1: The following evaluation scenarios are defined for NR SL positioning studies

o   Scenario 1. Out-of-coverage,

§  SL positioning should be able to work in stand-alone manner

§  Square model can be used and various inter-TP distance used for evaluation.

§  The movement from both reference UEs and measurement UE is considered in evaluation.

o   Scenario 2. In-coverage,

§  SL positioning can be used to assist Uu positioning.

§  SL positioning can be used in stand-alone manner

§  UMi/Uma/Indoor models (TR38.885) and InF-SH/InF-DH models (TS38.857) can be reused.

o   FFS: Specific parameters for the evaluation scenarios

·        Proposal 2: At least CDFs of horizontal and vertical (vertical error not necessarily applicable to all solutions and/or scenarios) positioning errors are used as performance metrics in NR SL positioning evaluations

·        Proposal 3: If RSU is considered for SL positioning evaluation, it can be treated as both UE type and gNB type.

·        Proposal 4: Study for measurement UE to decide measurement source(s) for SL positioning with proper criteria.

Decision: The document is noted.

R1-2203128         Evaluation of SL positioning           Nokia, Nokia Shanghai Bell

R1-2203163         Evaluation of SL positioning           Huawei, HiSilicon

R1-2203466         Evaluation methodology and performance evaluation for SL positioning               CATT, GOHIGH

R1-2203565         Evaluation of sideilnk positioning performance           vivo

R1-2203623         Discussion on evaluation for SL positioning ZTE

R1-2203719         Discussion on evaluation of SL positioning  LG Electronics

R1-2203822         Discussion on sidelink positioning evaluation methodology     xiaomi

R1-2203942         Evaluation of SL positioning           NEC

R1-2203979         Discussion on evaluation methodology of SL positioning         OPPO

R1-2204061         Discussion on sidelink positioning design     CENC

R1-2204131         Evaluation methodology for SL positioning  InterDigital, Inc.

R1-2204252         On Evaluation of SL positioning     Apple

R1-2204558         SL Positioning Evaluation Methodology       Lenovo

R1-2204834         SL positioning evaluation methodology        Fraunhofer IIS, Fraunhofer HHI

R1-2204949         Evaluation of SL positioning           Ericsson

R1-2205037         Sidelink Positioning Evaluation Assumptions and Results        Qualcomm Incorporated

[109-e-R18-Pos-03] – Chuangxin (ZTE)

Email discussion on evaluation of SL positioning by May 20

-        Check points: May 16, May 20

Decision: As per email decision posted on May 17^th,

Agreement

For SL positioning evaluation, V2X use case with highway and urban grid scenarios defined in TR 37.885 is supported.

·        The road configuration for urban grid and highway provided in TR 37.885 Annex A is reused

Agreement

For SL positioning evaluation in highway and urban grid scenarios, UE dropping option A defined in section 6.1.2 of TR 37.885 is used, i.e.

·        UE dropping option A is used for the highway scenario:

o   Vehicle type distribution: 100% vehicle type 2.

o   Clustered dropping is not used.

o   Vehicle speed is 140 km/h in all the lanes as baseline and 70 km/h in all the lanes optionally.

·        UE dropping option A is used for the urban grid scenario:

o   Vehicle type distribution: 100% vehicle type 2.

o   Clustered dropping is not used.

o   Vehicle speed is 60 km/h in all the lanes.

o   In the intersection, a UE goes straight, turns left, turns right with the probability of 0.5, 0.25, 0.25, respectively.

Agreement

For SL positioning evaluation in highway and urban grid scenarios, antenna model follows the description in TR 37.885 section 6.1.4.

·        Vehicle UE option 1 is the baseline (Vehicle UE antenna is modelled in Table 6.1.4-8 and 6.1.4-9 in TR 37.885)

·        Vehicle UE option 2 (two panels) can be optionally selected by companies

Agreement

For SL positioning evaluation in highway and urban grid scenarios, channel model follows description in TR 37.885 section 6.2. 

R1-2205227        Summary #1 of [109-e-R18-Pos-03] Email discussion on evaluation of SL positioning          Moderator (ZTE)

Agreement

·         The following performance metrics for SL positioning accuracy evaluation is defined:

o    For relative and absolute positioning

-          horizontal accuracy

-          vertical accuracy

o    For ranging

-          Ranging for distance, i.e. accuracy of distance

-          Ranging for angle, i.e. accuracy of angle

·         Companies are required to output

o    The percentiles of positioning accuracy error including 50%, 67%, 80%, 90% of UEs,

-          FFS others

o    And the CDF of positioning accuracy error

·         Performance metrics other than positioning accuracy, such as PHY/end-to-end latency, are up to companies

Agreement

·         For absolute positioning evaluation, anchor UEs’ locations are known

o    In the evaluation of SL only positioning

-          Anchor UEs are used to locate target UEs

o    In the evaluation of Joint Uu/SL positioning

-          Both BS and anchor UEs are used to locate target UEs

·         In the evaluation, relative positioning or ranging is performed between two UEs within X m

o    FFS X which can be different for different scenarios, e.g. highway, urban grid, etc.

o    Companies can consider to provide simulation results based on multiple X values

·         Positioning method should be reported by companies.

Agreement

For SL positioning evaluation,

·         The existing pattern and sequence of DL-PRS or positioning SRS can be reused as baseline for evaluation purpose.

o    Companies should provide the description if other pattern and sequence are evaluated,

o    AGC settling time is considered by companies

·         Explicit simulation of all links, individual parameters estimation is applied. Companies should provide description of applied algorithms for estimation of signal location parameters.

·         As baseline for absolute positioning, sidelink anchors location coordinates are perfectly known.

o    Uncertainty in the sidelink anchors location coordinates can be considered by companies

·         As baseline, Perfect synchronization between network and anchor UEs in the evaluation is assumed.

o    Network synchronization error and timing errors defined in TR 38.857 Table 6-1 can also be optionally used by companies for Synchronization between BS and BS, between BS and anchor UEs, and between anchor UEs.

Agreement

For SL positioning evaluation in highway and urban grid, the following simulation parameters are used for FR1

Evaluation parameters for SL positioning in FR1

R1-2205228        Summary #2 of [109-e-R18-Pos-03] Email discussion on evaluation of SL positioning          Moderator (ZTE)

From May 17^th GTW session

Agreement

·        For SL absolute positioning evaluation in highway scenario, the following options are supported

o   Alt 1 as optional: BS and UE-type RSU deployment follows TR 36.885, where wrap around method of 19*3 hexagonal cells with 500m ISD in Figure A.1.3-3 of TR 36.885 section A.1.3 is used.

o   Alt 2 as baseline: BSs are disabled, UE-type RSUs are uniformly located with 200m spacing on both sides of highway symmetrically.

§  Optional: staggered/unsymmetrical UE-type RSU distribution like

·       

·        For SL absolute positioning evaluation in urban grid scenario, BS and UE-type RSU deployment follows the description in TR 36.885 section A.1.3.

o   Companies can provide additional BS/ UE-type RSU deployment, e.g. additional UE-type RSUs are added to UE-type RSU deployment in TR 36.885

Note: For absolute positioning in highway, Alt 1 is assumed for evaluation of joint Uu/SL positioning, Alt 2 is assumed for evaluation of SL only positioning.

From May 20^th GTW session

Agreement

·        For evaluation of relative positioning or ranging in highway scenario

• BSs are disabled,
• UE type RSU may be disabled (as baseline) or enabled (as optional)
• If enabled, UE-type RSUs are uniformly located with 200m spacing on both sides of highway symmetrically.
• Optional: staggered/unsymmetrical UE-type RSU distribution like

·       

·        For evaluation of relative positioning or ranging in urban grid scenario

• BSs are disabled (baseline), or enabled (optional)
• companies should report their assumption
• UE type RSU may be disabled or enabled (companies should report their assumption)
• If enabled, UE type RSU deployment follows the description in TR 36.885 section A.1.3.
• If enabled, companies can provide additional RSU deployment, e.g. additional RSUs are added to RSU deployment in TR 36.885

Agreement

·        For SL positioning evaluation, simulation bandwidths of 10, 20, 40 and 100 MHz in FR1 can be used.

·        For SL positioning evaluation, simulation bandwidths of 100, 200 and 400MHz in FR2 can be used.

Agreement

·        For SL positioning evaluation of Public safety use cases

• Companies should provide detailed simulation assumptions including selected scenarios, channel models, center frequency, UE drop models, etc.
• Evaluation methodology on channel model of TR 36.843 is reused,
• Reuse the parameters of “Channel models” specified in Section A.2.1.2 of TR 36.843 with modification: Each component of channel model reuses what is specified in TR 38.901
• Anchor UE height should be reported by companies, e.g. anchor UE height is the same as TRP
• The performance metrics at least include absolute positioning accuracy and ranging with distance accuracy. Optionally, relative positioning accuracy or ranging with angle accuracy.

·        For SL positioning evaluation of Commercial use cases

• Companies should provide detailed simulation assumptions including selected scenarios, channel models, center frequency, UE drop models, etc.
• Evaluation methodology on channel model of TR 36.843 is reused,
• Reuse the parameters of “Channel models” specified in Section A.2.1.2 of TR 36.843 with modification: Each component of channel model reuses what is specified in TR 38.901
• Anchor UE height should be reported by companies, e.g. anchor UE height is the same as TRP
• The performance metrics at least include absolute positioning accuracy and ranging with distance accuracy. Optionally, relative positioning accuracy or ranging with angle accuracy

Decision: As per email decision posted on May 21^st,

Agreement

For SL positioning evaluation for IIOT use cases, InF-SH and/or InF-DH defined in TR 38.857 are used.

Agreement

For SL positioning evaluation on indoor factory scenarios, companies can select one of the following options for UE-2-UE channel model

·        Option 1: BS-2-UE channel model defined in TR 38.901 is revised

o   The UE parameters in the channel model defined in 38.901, e.g. UE height, antenna model, transmit power are used to replace gNB’s corresponding parameters.

§  Anchor UE height should be reported by companies, e.g. anchor UE height is the same as TRP.

·        Option 2: D2D channel mode from 36.843 A.2.1.2 is used

Agreement

For SL positioning evaluation on IIOT use case, the performance metrics at least include absolute accuracy and relative accuracy.

·         FFS how to select anchor UEs/RSU for absolute positioning, e.g. 20 anchor UEs/RSU are randomly deployed in the simulation area

9.5.1.3       Potential solutions for SL positioning

R1-2203566        Discussion on potential solutions for sidelink positioning    vivo

·        Proposal 1: Prioritize RTT and AoA for sidelink positioning considering to achieve relative positioning and ranging (e.g., ranging for distance and ranging for angle).

·        Proposal 2: Prioritize sidelink-based positioning. The combination  of SL positioning with Uu positioning is of low priority.

·        Proposal 3: Double-side RTT should be considered for SL positioning.

·        Proposal 4: Two antenna panels as the distributed antenna system can be considered for V2X positioning.

·        Proposal 5: Introduce a new SL reference signal (i.e., SL PRS) for SL positioning.

·        Proposal 6: The  of SL PRS can be associated with some UE information (e.g., pre-configured sequence ID, source ID).

·        Proposal 7: AGC and GP symbol are needed for the SL PRS pattern.

·        Proposal 8:

o   Support reuse of one or more comb sizes of DL-PRS for the SL-PRS pattern.

o   Partial staggered pattern can be considered for SL-PRS pattern considering SL structure (e.g, excluding the PSCCH symbol, AGC, or GP symbol for SL-PRS transmission).

·        Proposal 9:

o   SL PRS can be transmitted without PSSCH transmission in the resource pool.

o   SCI should be transmitted with the associated SL PRS.

o   Slot level SL PRS transmission should be supported.

·        Proposal 10: A dedicated resource pool should be studied for SL PRS transmission in Rel-18.

·        Proposal 11: SL mode 1 and mode 2 resource allocation mechanisms should be studied.

·        Proposal 12: SL mode 2 resource allocation can be used for SL PRS resource allocation with some modification (e.g., the SL PRS is used for RSRP measurement).

·        Proposal 13: The unified SL Positioning method can be introduced to support reporting one or more measurement results, similar to the TRP measurement result in TS 38.455.

·        Proposal 14: Suggest UE Rx – Tx time difference for SL positioning can be defined as T, which is the timing gap between transmission of SL-PRS and receiving SL-PRS to/from other UE.

·        Proposal 15: SL-PRS RSRP is needed to be introduced for SL-PRS measurement and reporting.

·        Proposal 16: SL-AoA is needed to be introduced for SL-PRS measurement and reporting.

·        Proposal 17: Unicast, groupcast and broadcast should be studied for SL positioning in Rel-18.

·        Proposal 18: Open-loop power control scheme should be studied for SL PRS.

Decision: The document is noted.

R1-2204385        Discussions on potential solutions for SL positioning            NTT DOCOMO, INC.

·        Proposal 1: For SL-positioning, at least RTT mechanism is supported.

·        Proposal 2: For SL-positioning, study whether TDOA mechanism can be supported or not, in consideration of time-misalignment among synchronizing UEs.

·        Proposal 3: Support the following SL-positioning procedure to obtain its own location.

o   Step 1: UE that requires its own location transmits information and/or signal to surrounding UEs

o   Step 2: The surrounding UEs receive the information and/or signal and transmit corresponding information and/or signal to the UE

·        Proposal 4: Study whether a case where a UE requires other UE’s location is considered in Rel-18 SL positioning or not.

·        Proposal 5: Study whether SL-positioning can use Uu measurement or not.

o   If supported, some UE in SL-positioning method can be replaced to gNB.

·        Proposal 6: Study availability of Uu positioning instead of SL-positioning in use cases assumed for SL-positioning.

o   If available, study priority order between Uu positioning and SL positioning and detailed procedure.

·        Proposal 7: For SL-positioning,

o   Study details on configuration/indication/report

o   Study measurement UE determination

o   Study cast-type to be used in SL-positioning method

·        Proposal 8: Support SL-positioning RS multiplexed on PSSCH.

·        Proposal 9: Study the following alternatives for SL-PRS.

o   Alt 1: Define SL-PRS as a new reference signal.

§  Configuration/Indication/Cast-type/Mapping resource/Mapping procedure (rate-matching vs puncturing)/Sequence

o   Alt 2: Define SL-PRS as an existing reference signal.

§  Configuration/Indication/Cast-type/Mapping resource modification

Decision: The document is noted.

R1-2203058         Considerations on sidelink reference signals for positioning purposes               FUTUREWEI

R1-2203129         Potential solutions for SL positioning            Nokia, Nokia Shanghai Bell

R1-2203164         Discussion on solutions to support SL positioning      Huawei, HiSilicon

R1-2203335         Consideration on potential solutions for SL positioning            Spreadtrum Communications

R1-2203467         Discussion on potential solutions for SL positioning  CATT, GOHIGH

R1-2203624         Discussion on potential solutions for SL positioning  ZTE

R1-2203659         Discussion on potential solutions for sidelink positioning         China Telecom

R1-2203720         Discussion on potential solutions for SL positioning  LG Electronics

R1-2203738         Considerations on potential solutions for SL positioning           Sony

R1-2203752         The potential solutions for sidelink positioning           MediaTek Inc.

R1-2203823         Discussion on sidelink positioning solutions xiaomi

R1-2203911         Discussion on Potential Solutions for SL Positioning Samsung

R1-2203943         Discussion on Potential Solutions for SL Positioning NEC

R1-2203980         Discussion on potential solutions for SL positioning  OPPO

R1-2204092         carrier phase measurement method for sidelink positioning      Locaila

R1-2204132         Potential solutions for SL positioning            InterDigital, Inc.

R1-2204253         Discussions on Potential solutions for SL positioning Apple

R1-2204310         Discussion on potential solutions for SL positioning  CMCC

R1-2204559         On Potential SL Positioning Solutions           Lenovo

R1-2204667         Views on potential solutions for SL positioning          Sharp

R1-2204755         Discussion on potential solutions for sidelink based positioning              CEWiT

R1-2204835         Potential solutions for SL positioning            Fraunhofer IIS, Fraunhofer HHI

R1-2204869         Views on potential solutions for SL positioning          ROBERT BOSCH GmbH

R1-2204940         Views on potential solutions for SL positioning          Intel Corporation

R1-2205151         Potential solutions for SL positioning            Ericsson (rev of R1-2204950)

R1-2205038         Potential Solutions for Sidelink Positioning  Qualcomm Incorporated

[109-e-R18-Pos-04] – Alex (Qualcomm)

Email discussion on potential solutions for SL positioning by May 20

-        Check points: May 16, May 20

Decision: As per email decision posted on May 16^th,

Agreement

Study power control mechanisms for SL-PRS transmission, including whether it is necessary.

R1-2205202        Moderator Summary #1 for [109-e-R18-Pos-04] Email discussion on potential solutions for SL positioning          Moderator (Qualcomm)

From May 17^th GTW session

Agreement

With regards to the Positioning methods supported using SL measurements study further the following methods:

• RTT-type solutions using SL
• Study both single-sided (also known as one-way) and double-sided (also known as two-way) RTT
• SL-AoA
• Include both Azimuth of arrival (AoA) and zenith of arrival (ZoA) in the study
• SL-TDOA
• SL-AoD
• Corresponds to a method where RSRP and/or RSRPP measurements similar to the DL-AoD method in Uu.
• Include both Azimuth of departure (AoD) and zenith of departure (ZoD) in the study
• Consider in the study at least the following aspects:
• Definition(s) of the corresponding SL measurements for each method
• Which method is applicable to absolute or relative positioning or ranging, including whether such categorization is needed to be discussed.
• For angle-based methods, antenna configuration consideration(s) using practical UE capabilities
• Per-panel location, if UE uses multiple panels.
• UE’s mobility, especially for V2X scenarios
• Impact of synchronization error(s) between UEs
• Existing SL measurements (e.g. RSSI, RSRP), and UE ID information etc, may be used.
• Note: The above categorization does not necessarily mean that there will be separate SL positioning methods specified, or whether there will be a unified SL Positioning method.

·        Note: When the study of carrier phase positioning and the evaluations of sidelink positioning have progressed, it can be reviewed whether carrier phase for sidelink can be considered in further work. Checkpoint at RAN1#110-e-Bis to see if sufficient information is available for this review.

·        Note: Companies are encouraged to describe the role of SL nodes and their interaction/coordination participating in each method.

Decision: As per email decision posted on May 19^th,

Agreement (Above agreement is revised from May 17^th GTW session as shown in red)

Agreement

With regards to the numerologies of the SL-PRS, limit the study to those supported for NR Sidelink.

·        Note 1: NR Sidelink supports {15, 30, 60 kHz} in FR1 and {60, 120 kHz} in FR2

·        Note 2: This doesn’t imply that SL-PRS FR2-specific optimization(s) are expected to be studied

Agreement

Study new reference signal for SL positioning/ranging using the existing PRS/SRS design and SL design framework as a starting point.

·        The study could at least include: Sequence design, frequency domain pattern, time domain pattern (e.g. number of symbols, repetitions, etc), time domain behavior, configuration/triggering/activation/de-activation of the SL-PRS, AGC time, Tx-Rx Turanround time, supportable bandwidth(s), multiplexing options with other SL channels, randomization/orthogonalization options.

·        Note: The study of existing SL reference signal for SL positioning/ranging is not precluded. Companies are encouraged to perform performance evaluation/comparison to investigate whether such reference signals can meet the positioning accuracy requirements.

Agreement

With regards to the configuration/activation/deactivation/triggering of SL-PRS, study the following options:

• Option 1: High-layer-only signaling involvement in the SL-PRS configuration
• No Lower layer involvement, e.g., SL-MAC-CE or SCI or DCI, for the activation or the triggering of a SL-PRS.
• Based on the study, this option may correspond to
• A SL-PRS configuration that is a single-shot or multiple shots
• A high-layer configuration that may be received from an LMF, a gNB, or a UE
• Option 2: High-layer and lower-layer signaling involvement in the SL-PRS configuration
• Lower-layer may correspond to SL-MAC-CE, or SCI, or DCI
• For example, high layer signaling can may be used for SL-PRS configuration and lower layer signaling can may be used for initiating SL positioning and/or configuration/triggering/activating/deactivating/indicating and potential resource indication/reservation transmission of SL-PRS.
• Option 3: Only lower-layer signaling involvement in the SL-PRS configuration
• Lower-layer may correspond to SL-MAC-CE, or SCI, or DCI
• Note 1: Include aspects in the study related to flexibility, overhead, latency, and reliability as/if needed.

Agreement

With regards to the Sidelink Positioning measurement report,

·        Study the contents of the measurement report  (e.g. time stamp(s), quality metric(s), ID(s), angular/timing/power measurements, etc)

·        Study the time domain behavior of the measurement report (e.g. one-shot, triggered, aperiodic, semi-persistent, periodic)

·        FFS whether the Sidelink Positioning measurement can be a high-layer report and/or a lower layer report.

Agreement

For the purpose of RAN1 discussion during this study item, at least the following terminology is used:

• Target UE: UE to be positioned (in this context, using SL, i.e. PC5 interface).
• Sidelink positioning: Positioning UE using reference signals transmitted over SL, i.e., PC5 interface, to obtain absolute position, relative position, or ranging information.
• Ranging: determination of the distance and/or the direction between a UE and another entity, e.g., anchor UE.
• Sidelink positioning reference signal (SL PRS): reference signal transmitted over SL for positioning purposes.
• SL PRS (pre-)configuration: (pre-)configured parameters of SL PRS such as time-frequency resources (other parameters are not precluded) including its bandwidth and periodicity.
• Continue discussion on additional terminology clarification(s) such as: Initiator UE, Responder UE, Sidelink Positioning group, reference UE, etc, including whether such terminology is needed within RAN1 discussion.

R1-2205457        Moderator Summary #2 for [109-e-R18-Pos-04] Email discussion on potential solutions for SL positioning          Moderator (Qualcomm)

From May 20^th GTW session

Agreement

For the purpose of RAN1 discussion during this study item, at least the following terminology is used:

·        Anchor UE: UE supporting positioning of target UE, e.g., by transmitting and/or receiving reference signals for positioning, providing positioning-related information, etc., over the SL interface.

o   FFS: clarification of the knowledge of the location of the anchor UE

Decision: As per email decision posted on May 21^st,

Agreement

With regards to the frequency domain pattern, study further a Comb-N SL-PRS design. Study at least the following aspects:

·        N>=1 (where N=1 corresponds to full RE mapping pattern)

·        Fully staggered SL-PRS pattern (e.g., M symbols of SL-PRS with comb-N with M=N and, at each symbol a different RE offset is used), Partially staggered SL-PRS pattern (e.g., M symbol(s) of SL-PRS with comb-N, with M<N, at each symbol a different RE offset is used), Unstaggered SL-PRS patterns (e.g., M symbol(s) of SL-PRS with comb- N, at each symbol a same RE offset is used, N > 1)

·        The number of symbols of SL-PRS within a slot

o   Any relation to the comb-N option

o   RE offset pattern repetitions within a slot

·        FFS: Other frequency domain pattern(s)

Agreement

For a potential new SL PRS, study further the following

·        Number of symbol(s) for AGC and/or Rx-Tx turnaround time

·        Conditions under which AGC training and/or Rx-Tx turnaround time are needed

Agreement

With regards to the SL Positioning resource allocation, study further the following 2 options for SL Positioning resource (pre-)configuration:

• Option 1: Dedicated resource pool for SL-PRS
• Include in the study at least the following aspects:
• which slots can be used, SL frame structure, SL positioning slot structure, multiplexing of SL-PRS with control information (if included in the same slot)
• positioning measurement report
• whether a dedicated frequency allocation (e.g., layer/BWP) is needed for SL PRS
• resource allocation procedure(s) of SL-PRS
• This option may or may not include control information (i.e., configuration/activation/deactivation/triggering of SL-PRS) for the purpose of SL positioning operation
• Option 2: Shared resource pool with sidelink communication.
• Include in the study at least the following aspects:
• co-existence between SL communication and SL positioning, backward compatibility
• Multiplexing considerations of SL-PRS with other PHY channels (PSCCH, PSSCH, PSFCH) and any modifications in the SL-slot structure

Agreement

With regards to the SL-PRS resource allocation, study the following two schemes:

·        Scheme 1: Network-centric operation SL-PRS resource allocation (e.g. similar to a legacy Mode 1 solution)

o   The network (e.g. gNB, LMF, gNB & LMF) allocates resources for SL-PRS

·        Scheme 2: UE autonomous SL-PRS resource allocation (e.g. similar to legacy Mode 2 solution)

o   At least one of the UE(s) participating in the sidelink positioning operation allocates resources for SL-PRS

o   Applicable regardless of the network coverage

·        FFS: potential mechanisms, if needed, for SL-PRS resource coordination across a number of transmitting UEs (e.g. IUC-like solutions).

·        Note: Other Schemes are not precluded to be studied

·        FFS how to handle resource allocation of SL-Positioning measurement report

9.5.2        Improved positioning accuracy, integrity, and power efficiency

9.5.2.1       Solutions for integrity of RAT dependent positioning techniques

R1-2203165         Error source for NR RAT-dependent positioning        Huawei, HiSilicon

R1-2203177         Initial Views on solutions for integrity of RAT-dependent positioning techniques               Nokia, Nokia Shanghai Bell

R1-2203336         Consideration on solutions for integrity of RAT dependent positioning techniques               Spreadtrum Communications

R1-2203468         Discussion on solutions for integrity of RAT dependent positioning techniques               CATT

R1-2203567         Discussion on solutions for integrity of RAT dependent positioning       vivo

R1-2203625         Discussion on integrity of RAT dependent positioning              ZTE

R1-2203739         Considerations on solution for integrity of RAT dependent positioning techniques               Sony

R1-2203912         Discussion on Integrity of RAT Dependent Positioning            Samsung

R1-2203965         Discussions on Integrity for NR Positioning OPPO

R1-2204133         Integrity for RAT dependent positioning techniques   InterDigital, Inc.

R1-2204311         Discussion on solutions for integrity of RAT-dependent positioning techniques               CMCC

R1-2204386         Discussion on solutions for integrity of RAT dependent positioning techniques   NTT DOCOMO, INC.

R1-2204523         Discussion on integrity of RAT dependent positioning techniques          LG Electronics

R1-2204560         Integrity for RAT-dependent positioning      Lenovo

R1-2204668         Views on solutions for integrity of RAT dependent positioning techniques               Sharp

R1-2204951         Solutions for integrity of RAT dependent positioning techniques            Ericsson

R1-2205039         Integrity for RAT dependent positioning       Qualcomm Incorporated

[109-e-R18-Pos-05] – Fumihiro (InterDigital)

Email discussion on integrity of RAT dependent positioning techniques by May 20

-        Check points: May 16, May 20

Decision: As per email decision posted on May 17^th,

Agreement

·        Study sources of error for timing-based positioning and angle-based positioning methods, focusing on the following aspects

o   Origin of the error source

§  e.g., At UE and/or network side

§  e.g., From assistance information, and/or measurements

o   Model of the error source (e.g., distribution, mean and/or standard deviation for integrity overbounding model, range)

o   Criteria to become an error source (e.g., whether it is quantifiable, how much influence an error source has on determination on integrity)

·        It is encouraged to provide evaluation assumptions (e.g., requirements in TS 38.101, TS 38.104, TS 38.133, evaluation assumptions in TR 38.857) if evaluation is used to determine a distribution, mean and standard deviation or range of values of an error source

·        UE-based/assisted DL positioning methods, UL and DL&UL positioning methods are considered in the study

Agreement

·        At least the following error sources for timing-based positioning methods are studied

o   TRP/UE measurements errors (e.g., ToA, Rx-Tx timing difference)

§  FFS: Effect of multipath/NLoS channels on TRP/UE measurement errors

o   Error in assistance data (e.g., TRP location, Inter-TRP synchronization errors (e.g., RTD))

o   TRP/UE Timing error

o   FFS: Further study identification of error sources resulting from the multipath/NLoS channel/radio propagation environment, including multipath/NLoS channel itself as an error source

·        Other error sources are not precluded

·        FFS: details of each error source, e.g., mean/standard deviation/range associated with each error

Agreement

·        At least the following error sources for angle -based positioning methods are studied

o   TRP/UE measurements errors (e.g., AoA, RSRP, RSRPP expectedAoD/AoA)

§  FFS: Effect of multipath/NLoS channels on TRP/UE measurement errors

o   Error in assistance data (e.g TRP location, TRP beam antenna information)

o   FFS: Further study identification of error sources resulting from the multipath/NLoS channel/radio propagation environment, including multipath/NLoS channel itself as an error source

·        Other error sources are not precluded

·        FFS: details of each error source, e.g., mean/standard deviation/range associated with each error

Decision: As per email decision posted on May 18^th,

Agreement

For the purpose of discussion of error sources, reuse the definitions for RAT-dependent integrity and update the references to GNSS in Section 8.1.1a in TS38.305 to also include RAT-dependent methods.

·        Note: The intention of the proposal is not to make text proposals for TS 38.305

·        FFS: whether to modify and/or how to modify, for the purpose of discussion in RAN1, terms in 8.1.1a in TS 38.305 (e.g., definitions for “Error”, “Bound”, “Time-to-Alert (TTA)”, “DNU”, “Residual Risk”, “irMinimum, irMaximum”) for RAT dependent positioning methods

Decision: As per email decision posted on May 21^st,

Agreement

In addition to the agreed aspects for the study, study the following aspects for error sources for timing/angle based positioning methods

·        Mapping between an error source and a positioning method (e.g., DL, UL, DL&UL positioning method)

o   e.g., error in TRP location can be an error source for UE-based DL-AoD

·        Other aspects are not precluded

Final summary in R1-2205344.

9.5.2.2       Improved accuracy based on NR carrier phase measurement

R1-2203469        Discussion on improved accuracy based on NR carrier phase measurement               CATT

·        Proposal 1: R18 SI should focus on reuse of existing R16 PRS and SRS first for reference signal.

·        Proposal 2: Candidate DL/UL measurements for NR CPP may include the carrier phase measurement (Phase Of Arrival, POA), differential carrier phase measurement (Phase Difference Of Arrival, PDOA)  and measurement quality indication. The PDOA can be the POA difference between different gNB/TRPs  or the POA difference between different antennas of same UE. The measurement quality indication can include one or combination of following items: LOS/NLOS indicator, Rician factor, SINR, and variance of CPP measurement, etc.

·        Proposal 3: Joint reporting of POA and TOA for smoothing TOA with POA can be studied to improve the traditional DL/UL-TDOA performance.

·        Proposal 4: At least the following two methods to eliminate the impact of ATA/AFA can be studied.

o   Method 1: UE reports both the value and time stamp of ATA and/or AFA to the network side.

o   Method 2: Network controls the effective time window of ATA and AFA for UE.

·        Proposal 5: Both time-domain and frequency-domain methods for carrier phase measurement with non-continuous signal can be studied.

·        Proposal 6: Both continuous location tracking algorithm and one-shot location calculation algorithm can be studied for solution for UE location calculation with integer ambiguity.

·        Proposal 7: Carrier phases measurements from two or more carrier frequencies are helpful for fast resolution of the integer ambiguity.

·        Proposal 8: Double differential technique with PRU can be used for solution for timing offset between TRPs.

·        Proposal 9: Reuse simulation assumption of InF-SH channel scenario in FR1 in Rel-17 for the simulation of CPP, where the key simulation parameters in Table 1 can be considered..

Decision: The document is noted.

R1-2203634        Use cases and applications on Carrier Phase Based Positioning for NR                Locaila

·        Proposal 1: Study new reference signaling efficient for supporting phase-based measurement method

·        Proposal 2: Investigate ambiguity resolution methods and necessary impact on the 5G NR system

·        Proposal 3: Study phase based DL-AoD measurement method and necessary impact on 5G NR system

Decision: The document is noted.

R1-2203626        Discussion on Carrier Phase Measurement Based Positioning           ZTE

·        Proposal 1: InF-SH is used for evaluation of carrier phase based positioning.

·        Proposal 2: The bandwidth (e.g., 100MHz) used for evaluation of carrier phase based positioning should be aligned among companies.

·        Proposal 3: Consider to specify carrier phase measurement based positioning in Rel-18.

·        Proposal 4: Discuss whether carrier phase measurement is an independent positioning method or is configured under each legacy positioning method.

·        Proposal 5: Discuss whether LMF based or UE based solution or both is supported. Also discuss whether UL or DL carrier phase measurement or both is supported.

·        Proposal 6: Discuss how the carrier phase estimation can be achieved based on the existing PRS or SRS, e.g. from frequency domain channel estimation or time domain channel estimation.

Decision: The document is noted.

R1-2203166         Discussion on NR carrier phase positioning  Huawei, HiSilicon

R1-2203178         Initial Views on improved accuracy based on NR carrier phase measurement               Nokia, Nokia Shanghai Bell

R1-2203337         Consideration on improved accuracy based on NR carrier phase measurement               Spreadtrum Communications

R1-2203568         Discussion on carrier phase measurement enhancements          vivo

R1-2203635         "Continuous PRS for improved carrier phase measurement Document for:               Discussion & Decision"    Dankook University

R1-2203660         Discussion on improved accuracy based on NR carrier phase measurement               China Telecom

R1-2203753         On carrier phase measurement        MediaTek Inc.

R1-2203824         Improved accuracy based on NR carrier phase measurement    xiaomi

R1-2203913         Discussion on NR Carrier Phase Measurement            Samsung

R1-2203966         Discussions on Carrier Phase Measurement for NR Positioning              OPPO

R1-2204134         Potential solutions for carrier phase based positioning InterDigital, Inc.

R1-2204312         Discussion on carrier phase positioning         CMCC

R1-2204387         Discussion on improved accuracy based on NR carrier phase measurement          NTT DOCOMO, INC.

R1-2204524         Discussion on OFDM based carrier phase measurement in NR LG Electronics

R1-2204561         On NR carrier phase measurements Lenovo

R1-2204669         Views on improved accuracy based on NR carrier phase measurement  Sharp

R1-2204807         Design Aspects of Carrier Phase Measurements for NR Positioning Enhancements               Intel Corporation

R1-2204836         NR carrier phase measurements for positioning          Fraunhofer IIS, Fraunhofer HHI

R1-2204952         Improved accuracy based on NR carrier phase measurement    Ericsson

R1-2205040         Phase Measurements in NR Positioning        Qualcomm Incorporated

[109-e-R18-Pos-06] – Ren (CATT)

Email discussion on improved accuracy based on NR carrier phase measurement by May 20

-        Check points: May 16, May 20

Decision: As per email decision posted on May 16^h,

Agreement

NR carrier phase positioning performance will be evaluated at least with the carrier phase measurements of a single measurement instance.

Decision: As per email decision posted on May 17^th,

Agreement

The impact of integer ambiguity on NR carrier phase positioning and potential solutions to resolve the integer ambiguity will be studied in the SI.

Decision: As per email decision posted on May 19^th,

Agreement

The study of the accuracy improvement based on NR carrier phase measurements in Rel-18 SI may include:

·        UE-based and UE-assisted carrier phase positioning,

·        UL carrier phase positioning and DL carrier phase positioning.

·        NR carrier phase positioning with the carrier phase measurements of one carrier frequency or multiple frequencies

·        Combination of NR carrier phase positioning with another standardized Rel. 17 positioning method, e.g., DL-TDOA, UL-TDOA, Multi-RTT, etc.

·        Note: The use of “carrier phase positioning” does not necessarily mean it is a standalone positioning method

·        FFS: whether SL carrier phase positioning is to be discussed in Rel-18 SI

Agreement

·        The impact of multipath for the carrier phase positioning will be evaluated during the SI

·        The methods of mitigating the impact of multipath for the carrier phase positioning will be studied during the SI, if it is considered to be necessary after the evaluation.

R1-2205164        FL Summary for improved accuracy based on NR carrier phase measurement               Moderator (CATT)

From May 20^th GTW session

Agreement

·        Reuse the simulation assumptions of NR Rel-16/17 for carrier phase positioning

o   Note: Optional modification of the simulation assumptions defined in NR Rel-16/17 are allowed only if needed.

·        The evaluation scenarios:

o   Baseline: InF-SH, InF-DH

o   Optional: IOO, Umi, Highway

§  Note 1: Other evaluation scenarios are not precluded.

§  Note 2: Existing Rel-17 DL/UL reference signals in Uu interface is to be used for the Highway scenario.

·        Frequency range:

o   Baseline: FR1

o   Optional: FR2

Agreement

·        In addition to the evaluation assumptions of NR Rel-16/17, the following error sources may also be considered during the evaluation:

o   Phase noise (FR2)

o   CFO/Doppler

o   Oscillator-drift

o   Transmitter/receiver antenna reference point location errors

o   Transmitter/receiver initial phase error

o   Phase center offset

·        Note: Other error sources are not precluded

·        Note: UE mobility can be considered in the evaluations

·        Note: one or more error sources can be evaluated jointly

·        Note: companies should provide the error sources model with their evaluations

Agreement

·        For the purposes of discussion, for NR downlink and/or uplink carrier phase positioning, the carrier phase (CP) at a RF frequency at a receiver is a phase that is a function of the signal propagation time from an Tx antenna reference point of a transmitter (e.g., a TRP or a UE) to a Rx antenna reference point of the receiver (e.g., a UE or a TRP).

o   The propagation time can be expressed in a fractional part of a cycle of the RF frequency and a number of integer cycles, but the CP may be independent of the number of integer cycles.

Agreement

The use of PRUs to facilitate NR carrier phase positioning can be evaluated in the SI by RAN1.

Final summary in R1-2205165.

9.5.2.3       LPHAP (Low Power High Accuracy Positioning)

Including discussions on requirements, evaluations, and potential enhancements.

R1-2203167         Requirements and evaluation methodology for LPHAP             Huawei, HiSilicon

R1-2203179         Initial Views on LPHAP    Nokia, Nokia Shanghai Bell

R1-2203470         Discussion on Low Power High Accuracy Positioning              CATT

R1-2203569         Discussion on Low Power High Accuracy Positioning              vivo

R1-2203627         Discussion on low power high accuracy positioning(LPHAP)  ZTE

R1-2203825         LPHAP (Low Power High Accuracy Positioning)       xiaomi

R1-2203914         Discussion on LPHAP       Samsung

R1-2203967         Discussion on Low Power High Accuracy Positioning              OPPO

R1-2204155         Discussions on Low Power High Accuracy Positioning (LPHAP) techniques               InterDigital, Inc.

R1-2204313         Discussion on low power high accuracy positioning   CMCC

R1-2204426         Discussion on Low Power High Accuracy Positioning              Quectel

R1-2204525         Discussion on LPHAP in idle/inactive state  LG Electronics

R1-2204562         LPHAP considerations      Lenovo

R1-2204670         Views on low power high accuracy positioning           Sharp

R1-2204953         On the requirements, evaluations and potential enhancements for Low Power High Accuracy Positioning)       Ericsson

R1-2205041         Requirements, Evaluations, Potential Enhancements for Low Power High Accuracy Positioning          Qualcomm Incorporated

[109-e-R18-Pos-07] – Jingwen (CMCC)

Email discussion on LPHAP by May 20

-        Check points: May 16, May 20

Decision: As per email decision posted on May 16^h,

Agreement

Confirm that use case 6 defined in TS 22.104 is the single representative use case for the study of LPHAP.

Agreement

At least the relative power unit is adopted as the performance metric to evaluate the power consumption of the Rel-17 RRC_INACTIVE state positioning and potential enhancements.

Agreement

A reference device (e.g., a mobile phone) with reference traffic type, reference battery capability, and reference battery life is defined for the purpose of identification of the performance gap that achieved by the Rel-17 RRC_INACTIVE state positioning baseline and the target battery life of LPHAP use case 6.

Agreement

·         Adopt the following parameters as the common evaluation parameters for the LPHAP evaluation:

o    Frequency range: FR1 (baseline); FR2 (optional)

o    SCS: 30kHz for FR1 (baseline); 120kHz for FR2 (optional)

o    BW of the DL PRS and UL SRS pos: 100MHz;

o    Single-sample measurement per position fix (baseline); 4-sample measurement per position fix (optional)

o    UE mobility: up to 3km/h

·         Note: It is up to each company to provide detailed power model and evaluation results on power consumption in FR2.

Agreement

In the LPHAP evaluation, the power consumption of 5GC data traffic is not modelled. Only the power consumption of the traffic type related to LPHAP positioning (e.g., obtaining/updating SRS configurations, DL PRS measurement reporting, etc.) is considered.

·         Note: This does not preclude the power consumption of paging monitoring in the baseline evaluation, but rather assumes that no power consumption of 5GC data traffic is considered during a power cycle.

Agreement

·        Adopt the following power consumption model common for the baseline evaluation of Rel-17 RRC_INACTIVE state positioning.

Agreement

·        Adopt the following power consumption model for UL SRS for positioning transmission.

Decision: As per email decision posted on May 19^h,

Agreement

·        In Rel-18 low power and high accuracy positioning, adopt the following requirement:

o   Horizontal positioning accuracy < 1 m for 90% of UEs

o   Positioning interval / duty cycle of 15-30 s

o   UE battery life of 6 months – 1 year

·        Note: Setting an exact value each from the set of positioning interval / duty cycle and UE battery life in the evaluation and identification of performance gap will be discussed separately when necessary.

Conclusion

·        At least when the positioning accuracy is evaluated without jointly evaluating the associated power consumption, the target horizontal positioning accuracy requirement on LPHAP of <1m can be achieved by Rel-16/17 positioning techniques with a positioning bandwidth of at least 100MHz.

·        The main aspect of RAN1 evaluation is on power consumption.

·        Note: This does not preclude the case that the positioning accuracy can be revisited, if found necessary at later stage.

Agreement

• Study further at least the following models and parameter values of conversion between the relative power unit and the battery life to identify the performance gap:
• Alt. 1: battery life is used as the metric to identify the gap
• Example:

• Alt. 2: relative power unit is adopted as the metric to identify the gap
• Example:

in which

§  C1 is the battery capacity of the reference device;

§  T1 is the battery life of the reference device;

§  P1 is the relative power unit obtained based on the reference traffic type;

§  X is the percentage of the power consumed by the reference traffic type;

§  C2 is the battery capacity of the LPHAP device;

§  P2 is the evaluated relative power unit of the LPHAP device;

§  P2_req is the target relative power unit of the LPHAP device;

§  T2_req is the target battery life of the LPHAP device

o   Examples of these parameters are provided as follows:

Decision: As per email decision posted on May 21^st,

Agreement

Adopt the following periodicity of DL PRS / UL SRS for positioning in the baseline evaluation of Rel-17 RRC_INACTIVE positioning:

·        1 DL PRS / UL SRS for positioning occasion per N I-DRX cycle(s);

o   Candidate values of N to evaluate is 1 and 8 for I-DRX cycle of 1.28s;

§  Note: Individual company may consider either one or both in the evaluation.

o   Candidate value of N to evaluate is 1 for I-DRX cycle of 10.24s.

Agreement

·        The I-DRX configuration is included in the baseline evaluation of Rel-17 RRC_INACTVIE positioning.

o   Note: This does not preclude the case where no I-DRX cycle nor paging is considered in the evaluation of potential solutions to maximize the battery life.

·        Adopt the following I-DRX cycle to evaluate:

o   1.28s (baseline); 10.24s (optional).

Agreement

·       Adopt the power consumption model, additional transition energy and total transition time of the three sleep types (deep sleep, light sleep, and micro sleep) in TR38.840 as the evaluation baseline:

·       FFS: whether/how an additional new ultra-deep sleep mode can be considered in the evaluation of potential solutions to maximize the battery life, including the determination of the relative power, additional transition energy and total transition time, if necessary.

Agreement

·        Adopt the following reference configuration and assumption for DL PRS to define the power consumption model for DL PRS measurement:

o   1 Number of PFL;

o   8 DL PRS resources per slot are measured;

o   DL PRS instance of smaller than or equal to 1 slot duration;

·        Adopt the following table as the power consumption model for DL PRS measurement (derived from Table 22 in TR38.840):

Agreement

·        For DL positioning, at least the following power components and parameter values are considered for the baseline evaluation of Rel-17 RRC_INACTIVE positioning:

o   For the UE-assisted DL positioning,

§  SSB proc. with 2 ms duration and the periodicity of I-DRX cycle;

§  Paging with 2 ms duration, the periodicity of I-DRX cycle, and group paging rate of 10%;

§  DL PRS measurement with 0.5 ms duration;

§  CG-SDT with 1ms duration and the periodicity of positioning interval;

§  RRCRelease after the CG-SDT can be optionally included with [1] ms duration;

§  (Optional) BWP switching with [1] ms duration;

§  (Optional) Intra-/inter-frequency RRM measurement in low SINR condition with [1] ms duration;

§  (Optional) RA-SDT (e.g., including CORSET0 + SIB1, PRACH, RAR, Msg 3/4/5) in case of CG-SDT is unavailable;

o   For the UE-based DL positioning,

§  SSB proc. with 2 ms duration and the periodicity of I-DRX cycle;

§  Paging with 2 ms duration, the periodicity of I-DRX cycle, and group paging rate of 10%;

§  DL PRS measurement with 0.5 ms duration;

§  (Optional) BWP switching with [1] ms duration;

§  (Optional) Intra-/inter-frequency RRM measurement in low SINR condition with [1] ms duration;

·        Note: The power component and parameter values for UE-assisted DL positioning is also applicable to the DL part of UE-assisted DL+UL positioning method.

·        Note: Individual company may consider additional power components and different parameter values in bracket in the evaluation.

·        Note: Companies are encouraged to provide the assumption on the timeline between different power consumption events in the evaluation of potential enhancements to reduce the transition times between different power states and to extend the sleeping time as much as possible.

Agreement

·        For UL positioning, at least the following power components and parameter values are considered for the baseline evaluation of Rel-17 RRC_INACTIVE positioning:

o   SSB proc. with 2 ms duration and the periodicity of I-DRX cycle;

o   Paging with 2 ms duration, the periodicity of I-DRX cycle, and group paging rate of 10%;

o   UL SRS for positioning transmission with 0.5 ms duration;

o   (Optional) BWP switching with [1] ms duration;

o   (Optional) Intra-/inter-frequency RRM measurement in low SINR condition with [1] ms duration;

·        Note: The power component and parameter values for UL positioning is also applicable to the UL part of UE-assisted DL+UL positioning method.

·        Note: Individual company may consider additional power components and different parameter values in bracket in the evaluation.

·        Note: Companies are encouraged to provide the assumption on the timeline between different power consumption events in the evaluation of potential enhancements to reduce the transition times between different power states and to extend the sleeping time as much as possible.

Final summary in R1-2205594.

9.5.3        Positioning for RedCap UEs

Including performance evaluation of existing positioning procedures and measurements with RedCap UEs. The result of the evaluation will be used to assess the necessity of enhancements and, if needed, identify enhancements.

R1-2203168        Discussion on RedCap positioning              Huawei, HiSilicon

·        Proposal 1: Set the following target requirements for RedCap positioning:

o   Horizontal positioning accuracy: <1m

o   Vertical positioning accuracy: <3m

·        Proposal 2: Identify positioning solutions suitable for RedCap UEs to achieve high accuracy positioning, i.e., sub-meter positioning accuracy.

Decision: The document is noted.

R1-2203968        Discussion on Positioning for RedCap UEs              OPPO

·        Proposal 1: Regarding the positioning support for RedCap UEs, support the following two categories of use cases:

o   Commercial use cases mainly for wearables

o   IIoT use cases mainly for industrial wireless sensors

·        Proposal 2: To evaluate positioning performance of RedCap UEs, support the following scenarios and evaluation assumptions:

o   For commercial use cases, select one or two of the following cases defined in Section 6.1 of TR 38.855

§  Case 1: Indoor Office

§  Case 2: UMi street canyon

o   For IIoT use cases, select one or two of the following cases defined in Section 6 of TR 38.857

§  Case 3: InF-SH

§  Case 4: InF-DH

o   FR1 is the first priority

o   For the detailed information of evaluation assumptions for each case, refer to TR 38.855 and TR 38.857.

·        Proposal 3: The support of positioning for RedCap UEs and any potential enhancement should not have large impact on the cost of RedCap UEs.

·        Proposal 4: The requirements of positioning performance for RedCap UE should be lower than that of normal UEs.

o   FFS: the exact values of requirements

Decision: The document is noted.

R1-2205042        Positioning for Reduced Capabilities UEs Qualcomm Incorporated

·        Proposal 1: Send LS to RAN4 to ask them to include positioning requirements derived using simulation assumptions wherein 1 Rx is assumed at the UE.

·        Proposal 2: For TDD scenarios,

o   We propose to reuse NR Rel-16/17 Evaluation assumptions for InH, and UMI FR1 scenarios as agreed in RAN1 #94-Bis for 4 GHz and 2 GHz.

§  Support adding optionally to evaluate the UMI FR1 cases with DeltaTau modeling similar to the one introduced for InF scenarios.

o   For FR1 FDD scenario introduce a new Urban Macro at 700 MHz with 500m ISD according to the simulation assumptions shown below.

o   For FR2 TDD Redcap, reuse the NR Rel-16/17 FR2 simulation assumptions with 100 MHz PRS bandwidth.

·        Proposal 3: Support Enhancements for Redcap devices, in both FR1 and FR2, to enable reaching a horizontal accuracy performance close to the NR Rel-17 positioning requirements at least in a subset of evaluation scenarios.

·        Proposal 4: Study inter & intra-slot repetition of a DL PRS resource for the purpose of enabling receive PRS hopping for both FR1 and FR2.

·        Proposal 5: Study inter & intra-slot repetition of a SRS resource for positioning for the purpose of enabling transmit SRS hopping for both FR1 and FR2.

·        Proposal 6: Study PRS/SRS overlapping configuration for the purpose of enabling phase estimation across PRS hops both FR1 and FR2.

·        Proposal 7: Study DL-PRS/ SRS resource configuration for the purpose of enabling transmitter PRS hopping.

·        Proposal 8: For the purpose of Redcap positioning enhancements, study supporting Phase-Difference AoD.

·        Proposal 9: For the purpose of Redcap positioning enhancements, study supporting Positioning measurements (RSTD, UE Rx-Tx, RSRPP) derived on SSB, TRS.

·        Proposal 10: For the purpose of Redcap positioning enhancements, study supporting M-RTT using SRS-MIMO.

Decision: The document is noted.

R1-2203180         Initial Views on Positioning for RedCap UEs              Nokia, Nokia Shanghai Bell

R1-2203471         Discussion on positioning for RedCap UEs   CATT

R1-2203570         Discussion on positioning for RedCap UEs   vivo

R1-2203628         Discussion on Positioning for RedCap UE    ZTE

R1-2203696         Discussion on positioning support for RedCap UEs    NEC

R1-2203740         Discussion on positioning for RedCap UEs   Sony

R1-2203754         The potential solutions for RedCap UEs for positioning            MediaTek Inc.

R1-2203826         Initial views on the positioning for RedCap UEs         xiaomi

R1-2203915         Discussion on Positioning for RedCap Ues   Samsung

R1-2204157         Evaluation assumptions and potential solutions for positioning for RedCap UEs               InterDigital, Inc.

R1-2204254         Discussions on Positioning for RedCap UEs Apple

R1-2204314         Discussion on RedCap positioning  CMCC

R1-2204388         Discussion on positioning for RedCap UEs   NTT DOCOMO, INC.

R1-2204425         Discussion on Positioning for RedCap UEs  Quectel

R1-2204526         Discussion on positioning support for RedCap UEs    LG Electronics

R1-2204563         Positioning for RedCap devices      Lenovo

R1-2204671         Views on positioning for RedCap UEs          Sharp

R1-2204808         On enhancements for NR positioning support of RedCap UEs Intel Corporation

R1-2204954         Positioning for RedCap UEs            Ericsson

[109-e-R18-Pos-08] – Florent (Ericsson)

Email discussion on positioning for RedCap UEs by May 20

-        Check points: May 16, May 20

Decision: As per email decision posted on May 15^h,

Agreement

For evaluation of RedCap UE positioning performances, all RAT based positioning methods can be considered. Sources should detail the chosen method(s) when presenting performance evaluations.

Decision: As per email decision posted on May 19^h,

Agreement

For evaluation of positioning performance of redcap UEs, adopt the general parameters are detailed in the table below

·        TBD parameters are discussed separately

 Table 6-1: Common scenario parameters applicable for all scenarios for Redcap UEs evaluations

Agreement

For the evaluation of RedCap positioning, the following bandwidth can be evaluated:

·        FR1: 20MHz baseline, 5MHz optional

·        FR2: 100MHz

Agreement (further updated on May 21^st as shown in red)

·        Adopt the following table for the UE model parameters

R1-2205526        Feature Lead Summary#1 for [109-e-R18-Pos-08] Positioning for RedCap Ues               Moderator (Ericsson)

From May 20^th GTW session

Agreement

The following scenarios are evaluated for positioning performance of Redcap

·        Baseline: (Case 1): Umi street canyon, as described in Table 6.1-1-4 of 38.855

·        Optional outdoor:

o   (Case 2): Uma, as described in Table 6.1-1-6 of 38.855

o   (Case 3): Rma (FFS details of the scenario)

·        Baseline: (Case 4): InF-SH as described in Table 6.1-1 of 38.857

·        Optional indoor: (Case 5) Indoor Open Office, as described in Table 6.1-1-3 of 38.855

·        Optional indoor: (Case 6) InF-DH as described in Table 6.1-1 of 38.857

Agreement

The FR2 UE antenna configuration is as follow:

·        (M, N, P, Mg, Ng) = (1, 2, 2, 1, 1) as minimum antenna configuration (baseline)

·        (M, N, P, Mg, Ng) = (2, 2, 2, 1, 1) as optional configuration.

Agreement

The evaluation methodology for RedCap UEs positioning performance uses DL PRS and/or UL SRS for positioning.

·        The methodology does not define any baseline reference signal configuration. Sources should detail the chosen configuration of reference signal(s) when presenting performance evaluations.

Agreement

For evaluation of positioning performance of redcap UEs in 700MHz band, the gNB antenna model is:

·        gNB antenna configuration from TR38.830, (M,N,P,Mg,Ng) = (4,2,2,1,1), (dH, dV) = (0.5, 0.8)λ

Decision: As per email decision posted on May 21^st,

Agreement

Use 2Rx and 1Tx for baseline number of UE branches in FR2 in the UE antenna configuration table for RedCap UEs evaluation.

·        FFS: optional configurations for number of UE branches in FR2.

Final summary in R1-2205636.

9.5.44        Other

R1-2203181         Initial Views on Other topics for Positioning Nokia, Nokia Shanghai Bell

R1-2203472         Discussion on solutions of carrier phase positioning in multipath scenarios               CATT

R1-2203571         Discussion on PRS measurement in IDLE state           vivo

R1-2203629         Discussion on Positioning with Multiple Frequency Layers (Carriers)    ZTE

R1-2203916         Discussion on expended and improved NR positioning             Samsung

R1-2204158         Efficient usage of available bandwidths for positioning             InterDigital, Inc.

R1-2204916         Considerations on the support of PRS/SRS bandwidth aggregation        Huawei, HiSilicon, China Unicom

R1-2204955         Considerations for PRS/SRS bandwidth aggregation  Ericsson

 RAN1#110

9.5       Study on expanded and improved NR positioning

Please refer to RP-221814 for detailed scope of the SI.

R1-2208147        Session notes for 9.5 (Study on expanded and improved NR positioning)       Ad-Hoc Chair (Huawei)

[110-R18-Pos] Email to be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc – Debdeeep (Intel)

R1-2207458         Draft TR 38.859 v001: Study on expanded and improved NR positioning            Intel Corporation, CATT, Ericsson

R1-2208157         Draft TR 38.859 v010: Study on expanded and improved NR positioning            Intel Corporation, CATT, Ericsson

R1-2208267        Draft TR 38.859 v010: Study on expanded and improved NR positioning               Intel Corporation, CATT, Ericsson

Agreement

The draft TR in R1-2208267 is agreed in principle. TR38. 859 is endorsed as v0.1.0 in R1-2208275.

9.5.1        Sidelink positioning

9.5.1.1       SL positioning scenarios and requirements

Including specific target performance requirements

R1-2205836         SL positioning scenarios and requirements   Nokia, Nokia Shanghai Bell

R1-2205853         Discussion on SL positioning scenarios and requirements         LG Electronics

R1-2205866         Remaining issues of scenarios and requirements for sidelink positioning               Huawei, HiSilicon

R1-2205899         Discussion on scenarios and requirements for SL positioning   ZTE

R1-2206044         Discussion on SL positioning scenarios and requirements         vivo

R1-2206066         Discussion on requirements for sidelink positioning   TOYOTA Info Technology Center

R1-2206122         Considerations on SL positioning scenarios  Sony

R1-2206238         SL positioning scenarios and requirements   NEC

R1-2206287         Discussion on SL positioning scenarios and requirements         OPPO

R1-2206403         Discussion on SL positioning scenarios and requirements         CATT, GOHIGH

R1-2206496         Potential SL Positioning Scenarios and Requirements Lenovo

R1-2206588         On scenarios and requirements for SL positioning      Intel Corporation

R1-2206829         On SL Positioning Scenarios and Requirements          Samsung

R1-2206916         Remaining issues on SL positioning scenarios and requirements             CMCC

R1-2207071         Further discussion on sidelink based positioning requirements & scenarios               CEWiT

R1-2207085         Discussions on SL positioning scenario and requirements         InterDigital, Inc.

R1-2207236         Sidelink Positioning Scenarios and Requirements       Qualcomm Incorporated

R1-2207282         Views on SL positioning scenarios and requirements Sharp

R1-2207340         Discussion on Sidelink positioning scenarios and requirements Apple

R1-2207507         Views on SL positioning scenarios and requirements ROBERT BOSCH GmbH

R1-2207577         Discussion on sidelink positioning scenarios and requirement  Xiaomi

R1-2207618         Scenarios and requirements for sidelink positioning   Ericsson

R1-2207626         Considerations on sidelink positioning in NR              ITL

R1-2207738        FL summary #1 on SL positioning scenarios and requirements        Moderator (Intel)

From Monday session

Agreement

·        For ranging between two devices, ranging direction accuracy is defined as accuracy of angle of arrival (AoA) at a receiving node.

·        The following requirements on ranging direction accuracy are considered:

o   Set A: Y = ±15° for 90% of the UEs

o   Set B: Y = ±8° for 90% of the UEs

o   Note 1: For evaluations of ranging direction accuracy, companies are expected to report:

§  whether each of the two requirements are satisfied, and

§  %-ile of UEs satisfying the target positioning accuracy for a requirement that may not be satisfied with 90%.

o   Note 2: target positioning requirements may not necessarily be reached for all scenarios and deployments.

o   Note 3: all positioning techniques may not achieve all positioning requirements in all scenarios.

Agreement

·        Confirm the following working assumption on positioning accuracy requirements for V2X with the changes indicated below:

o   For evaluation of V2X use-cases for SL positioning, the following accuracy requirements are considered:

§  Set A (similar to “Set 2” defined in TR 38.845)

·        Horizontal accuracy of 1.5 m (absolute and or relative); Vertical accuracy of 3 m (absolute and or relative) for 90% of UEs

§  Set B (similar to “Set 3” defined in TR 38.845)

·        Horizontal accuracy of 0.5 m (absolute and or relative); Vertical accuracy of 2 m (absolute and or relative) for 90% of UEs

§  Note 1: For evaluated SL positioning methods, companies are expected to report:

·        whether each of the two requirements are satisfied, and

·        %-ile of UEs satisfying the target positioning accuracy for a requirement that may not be satisfied with 90%.

§  Note 2: target positioning requirements may not necessarily be reached for all scenarios and deployments

§  Note 3: all positioning techniques may not achieve all positioning requirements in all scenarios

Agreement

·        Confirm the following working assumption on positioning accuracy requirements for IIoT:

o   For evaluation of IIoT use-cases for SL positioning solutions, the following accuracy requirements are considered:

§  For horizontal accuracy,

·        Set A: 1 m (absolute or relative) for 90% of UEs

·        Set B: 0.2 m (absolute or relative) for 90% of UEs

§  For vertical accuracy,

·        Set A: 1 m (absolute or relative) for 90% of UEs

·        Set B: 0.2 m (absolute or relative) for 90% of UEs

o   Relative speed: up to 30 km/hr.

o   Note 1: For evaluated SL positioning methods, companies are expected to report:

§  whether each of the two requirements are satisfied, and

§  %-ile of UEs satisfying the target positioning accuracy for a requirement that may not be satisfied with 90%.

o   Note 2: target positioning requirements may not necessarily be reached for all scenarios and deployments

o   Note 3: all positioning techniques may not achieve all positioning requirements in all scenarios

Conclusion

Further prioritization amongst the identified use-cases for SL positioning is not pursued during this SI in RAN1.

Final summary in R1-2208158.

9.5.1.2       Evaluation of SL positioning

Including evaluation methodology and performance evaluation results

R1-2205837         Evaluation of SL positioning           Nokia, Nokia Shanghai Bell

R1-2205854         Discussion on evaluation of SL positioning  LG Electronics

R1-2205867         Evaluation assumptions and results for SL positioning              Huawei, HiSilicon

R1-2205900         Discussion on evaluation of SL positioning  ZTE

R1-2206045         Evaluation of sidelink positioning performance           vivo

R1-2206123         Initial Performance Evaluation of SL Positioning       Sony

R1-2206239         Evaluation of SL positioning           NEC

R1-2206288         Remaining details on evaluation methodology of SL positioning            OPPO

R1-2206404         Evaluation methodology and performance evaluation for SL positioning               CATT, GOHIGH

R1-2206830         Discussion on Evaluation for SL Positioning Samsung

R1-2207072         Discussion on evaluation methods and results of sidelink based positioning               CEWiT

R1-2207086         Evaluation results for SL positioning             InterDigital, Inc.

R1-2207124         Evaluation methodology for SL positioning  Fraunhofer IIS, Fraunhofer HHI

R1-2207237         Sidelink Positioning Evaluation Assumptions and Results        Qualcomm Incorporated

R1-2207508         Views on Evaluation of SL positioning for VRU Protection     ROBERT BOSCH GmbH

R1-2207578         Discussion on evaluation of sidelink positioning         Xiaomi

R1-2207605         FL summary#1 for SL positioning evaluation              ZTE

R1-2207606         FL summary#2 for SL positioning evaluation              ZTE

R1-2207619         Simulation assumptions and evaluations for  NR SL positioning             Ericsson

R1-2207686         SL Positioning Evaluation Methodology and Performance       Lenovo  (rev of R1-2206497)

R1-2207605        FL summary#1 for SL positioning evaluation         ZTE

From Monday session

Agreement

For SL positioning evaluation in IIOT use case, companies should report how to drop anchor UEs and how to select anchor UEs

R1-2207606        FL summary#2 for SL positioning evaluation         ZTE

From Wed session

Agreement

Adopt the tables in section 3 of R1-2207606 as templates to collect SL positioning simulation results from each company.

Agreement

For SL positioning evaluation purpose, the following assumptions are further adopted

·        Companies should report whether SL-PRS and other SL signals are FDMed or not FDMed, and whether other SL signals are present

·        Adopting system level simulations (rather than the link level simulations) as the baseline tool

·        For SL positioning evaluation in highway scenario or urban grid scenario, the performance metrics can include absolute horizontal accuracy, relative horizontal accuracy, ranging with distance accuracy, and ranging with direction accuracy (optionally).

·        In highway and urban grid scenarios, companies can further consider other UE types, e.g. pedestrian UE or VRU devices.

Agreement

In the evaluation, relative positioning or ranging is performed between two UEs within X m, where X value(s) are reported by companies, and companies should also report the minimum distance used in the evaluations for each use case. The assumption used for X will be included in the TR for each set of results.

9.5.1.3       Potential solutions for SL positioning

R1-2205746         Potential sidelink positioning solutions         FUTUREWEI

R1-2205838         Potential solutions for SL positioning            Nokia, Nokia Shanghai Bell

R1-2205855         Discussion on potential solutions for SL positioning  LG Electronics

R1-2205868         Discussion on solutions to support SL positioning      Huawei, HiSilicon

R1-2205901         Discussion on potential solutions for SL positioning  ZTE

R1-2205994         Discussion on potential solutions for SL positioning  Spreadtrum Communications

R1-2206046         Discussion on potential solutions for sidelink positioning         vivo

R1-2206124         Discussion on potential solutions for SL positioning  Sony

R1-2206240         Discussion on Potential Solutions for SL Positioning NEC

R1-2206289         Discussion on potential solutions for SL positioning  OPPO

R1-2206405         Discussion on potential solutions for SL positioning  CATT, GOHIGH

R1-2206498         On Potential SL Positioning Solutions           Lenovo

R1-2206589         Potential solutions for SL positioning            Intel Corporation

R1-2206693         Discussion on potential solutions for sidelink positioning         China Telecom

R1-2206831         Discussion on Potential Solutions for SL Positioning Samsung

R1-2206917         Discussion on potential solutions for SL positioning  CMCC

R1-2207073         Discussion on enhancement for sidelink positioning support    CEWiT

R1-2207087         Potential solutions for SL positioning            InterDigital, Inc.

R1-2207125         Potential solutions for SL positioning            Fraunhofer IIS, Fraunhofer HHI

R1-2207238         Potential Solutions for Sidelink Positioning  Qualcomm Incorporated

R1-2207283         Views on potential solutions for SL positioning          Sharp

R1-2207341         Discussions on Potential solutions for SL positioning Apple

R1-2207411         Discussion on potential solutions for SL positioning  NTT DOCOMO, INC.

R1-2207443         Discussion on handling Anchor UE DENSO AUTOMOTIVE

R1-2207479         The potential solutions for sidelink positioning           MediaTek Inc.

R1-2207484         Discussion on sidelink positioning  ASUSTeK

R1-2207579         Discussion on sidelink positioning solutions Xiaomi

R1-2207620         On potential solutions for SL positioning      Ericsson

R1-2207846         Moderator Summary #1 on potential solutions for SL positioning           Moderator (Qualcomm)

R1-2207875        Moderator Summary #2 on potential solutions for SL positioning    Moderator (Qualcomm)

From Wed session

Agreement

With regards to the Positioning methods supported using at least SL measurements, potential candidate positioning methods include at least the following:

• RTT-type solution(s) using SL
• SL-AoA
• SL-TDOA
• Note: other methods can still be studied
• Note: The above categorization does not necessarily mean that there will be separate SL positioning methods specified. 

Agreement

A new reference signal should be introduced for supporting SL positioning/ranging.

Agreement

Regarding SL-PRS resource allocation, both Scheme 1 and Scheme 2 should be introduced for supporting SL positioning/ranging:

·        Scheme 1: Network-centric operation SL-PRS resource allocation (e.g. similar to a legacy Mode 1 solution)

o   The network (e.g. gNB, LMF, gNB & LMF) allocates resources for SL-PRS.

·        Scheme 2: UE autonomous SL-PRS resource allocation (e.g. similar to legacy Mode 2 solution)

o   At least one of the UE(s) participating in the sidelink positioning operation allocates resources for SL-PRS

Agreement

With regards to the SL Positioning resource allocation, one of the following alternatives should be introduced for supporting SL positioning/ranging:

• Alt. 1: only dedicated resource pool(s) can be (pre-)configured for SL-PRS
• Alt. 2: either dedicated resource pool(s) and/or a shared resource pool(s) with sidelink communication can be (pre-) configured for SL-PRS
• Note: whether other signals/channels can be present in the dedicated resource pool can be further discussed

R1-2207974        Moderator Summary #3 on potential solutions for SL positioning    Moderator (Qualcomm)

Agreement

For the content of the sidelink positioning measurement report, potential elements may include at least the following:

·        One or more sidelink positioning measurement(s)

·        Timestamp(s) associated with a sidelink positioning measurement

·        Quality metric(s) associated with a sidelink positioning measurement

·        Identification Information for a sidelink positioning measurement

·        FFS any detail for the above

Agreement

For the sequence of the new reference signal for SL positioning/ranging, down select between Alt 1 and Alt 2:

• Alt. 1: pseudorandom-based. Use existing sequence of DL-PRS as a starting point.
• Alt. 2: ZC-based (SRS sequence as a starting point)

Agreement

With regards to the frequency domain pattern, a Comb-N SL-PRS occupying M symbol(s) design should be introduced for the support of NR SL positioning

·        Note: there could be multiple values for M, N

Agreement

Regarding Scheme 2 SL-PRS resource allocation, study at least the following aspects:

·        Resource selection mechanism for SL-PRS

·        Inter-UE coordination

·        Aspects for congestion control mechanisms for SL-PRS

R1-2208186        Moderator Summary #4 on potential solutions for SL positioning    Moderator (Qualcomm)

Agreement

·        With regards to the configuration/activation/deactivation/triggering of SL-PRS, Option 3 from the previous corresponding RAN1 #109 agreement will not be considered further.

·        With regards to reservation of SL-PRS, it can be considered based on the Option 1 or Option 2 from the previous corresponding RAN1 #109 agreement.

Agreement

With regards to the frequency domain pattern for multi-symbol SL-PRS, prioritize partially and fully staggered SL-PRS.

·        Note: this does not preclude comb N=1

·        FFS: single symbol SL-PRS, if supported

9.5.2        Improved positioning accuracy, integrity, and power efficiency

9.5.2.1       Solutions for integrity of RAT dependent positioning techniques

R1-2205869         Error source for NR RAT-dependent positioning        Huawei, HiSilicon

R1-2205902         Discussion on integrity of RAT dependent positioning              ZTE

R1-2205995         Discussion on error sources for RAT-dependent positioning     Spreadtrum Communications

R1-2206047         Discussion on solutions for integrity of RAT dependent positioning       vivo

R1-2206125         Considerations on Integrity for RAT dependent positioning     Sony

R1-2206273         Discussions on Integrity for NR Positioning OPPO

R1-2206406         Discussion on solutions for integrity of RAT dependent positioning techniques               CATT

R1-2206490         Views on solutions for integrity of RAT-dependent positioning techniques               Nokia, Nokia Shanghai Bell

R1-2206499         Integrity aspects for RAT-dependent positioning        Lenovo

R1-2206650         Error source for NR RAT-dependent positioning integrity        Xiaomi

R1-2206832         Discussion on Integrity of RAT Dependent Positioning            Samsung

R1-2206918         Discussion on integrity for RAT-dependent positioning            CMCC

R1-2207088         Discussion on integrity for RAT dependent positioning techniques        InterDigital, Inc.

R1-2207239         Integrity for RAT dependent positioning       Qualcomm Incorporated

R1-2207284         Views on solutions for integrity of RAT dependent positioning techniques               Sharp

R1-2207412         Discussion on solutions for integrity of RAT dependent positioning techniques   NTT DOCOMO, INC.

R1-2207621         Error Sources characterization for integrity of RAT dependent positioning techniques               Ericsson

R1-2207744        FL summary #1 on integrity of RAT dependent positioning techniques               Moderator (InterDigital)

From Monday session

Agreement

·        For LMF-based positioning integrity mode, at least the followings are error sources for timing related measurements :

o   RSTD measurement is an error source for DL-TDOA

o   RTOA measurement is an error source for UL-TDOA

o   UE Rx-Tx time difference measurement is an error source for Multi-RTT

o   gNB Rx-Tx time difference measurement is an error source for Multi-RTT

·        FFS : Model of the error source (e.g., distribution, mean and/or standard deviation for integrity overbounding model, range)

·        Note : Definition of “LMF-based positioning integrity mode” can be found in Table 9.4.1.1.1 in TR 38.857

Agreement

·        For LMF-based positioning integrity mode, at least angle of arrival measurement is an error source for UL-AoA

·        FFS : Model of the error source (e.g., distribution, mean and/or standard deviation for integrity overbounding model, range)

·        FFS: The error can be expressed as the error of the AoA/ZoA in LCS or GCS or the error of a defined function of AoA/ZoA in LCS.

·        Note : Definition of “LMF-based positioning integrity mode” can be found in Table 9.4.1.1.1 in TR 38.857

R1-2207922        FL summary #2 on integrity of RAT dependent positioning techniques               Moderator (InterDigital)

Agreement

For UE-based positioning integrity mode, at least the following are error sources in assistance data :

• TRP location (e.g., NR-TRP-LocationInfo in TS 37.355) and Inter-TRP synchronization (e.g., NR-RTD-Info in TS 37.355) are error sources for DL-TDOA
• TRP location (e.g., NR-TRP-LocationInfo in TS 37.355) is an error source for DL-AoD
• FFS: whether boresight direction of DL-PRS (e.g., NR-DL-PRS-BeamInfo in TS 37.355) is an error source
• FFS: whether beam information of DL-PRS (e.g., NR-TRP-BeamAntennaInfo in TS 37.355) is an error source
• FFS : Model of the error source (e.g., distribution, mean and/or standard deviation for integrity overbounding model, range)
• Other error sources are not precluded
• FFS : Applicability of the above error sources to LMF-based positioning integrity mode
• Note : Definition of “UE-based positioning integrity mode” can be found in Table 9.4.1.1.1 in TR 38.857

Agreement

For LMF-based positioning integrity mode, ARP location (e.g., ARPLocationInformation in TS 38.455) is an error source for UL-AoA.

• FFS : Model of the error source (e.g., distribution, mean and/or standard deviation for integrity)
• Note : Definition of “LMF-based positioning integrity mode” can be found in Table 9.4.1.1.1 in TR 38.857
• FFS : Whether the error statistics of ARP location is available at the gNB
• Other error sources are not precluded

Agreement

For LMF-based positioning integrity mode, at least inter-TRP synchronization is an error source for UL-TDOA.

• FFS : Specification impact of inter-TRP synchronization as an error source for UL-TDOA
• Note : Definition of “LMF-based positioning integrity mode” can be found in Table 9.4.1.1.1 in TR 38.857

Agreement

Study the distribution of RSTD, RTOA and UE/gNB Rx-Tx time measurement error considering the following aspects:

• Whether TEG-related timing error is an independent error source from timing related measurement error (e.g., RTOA, RSTD, UE/gNB Rx-Tx time difference)
• Whether the measurement error is considered for each ToA or for the reported RSTD value
• Other Details (e.g., mean and standard deviation)

Note : it is encouraged to provide the evaluation assumptions used by companies (e.g., requirements in TS 38.101, TS 38.104, TS 38.133, evaluation assumptions in TR 38.857, LOS/NLOS probability, measurement algorithm) and results (e.g., error histogram) if evaluation is used to determine the distribution, mean and standard deviation or range of values of an error source.

R1-2208189        FL summary #3 on integrity of RAT dependent positioning techniques               Moderator (InterDigital)

Agreement

Study the distribution of arrival measurement error focusing on the following aspects

• Whether the angle of arrival measurement error can be expressed as the error of the AoA/ZoA in LCS or GCS or the error of a defined function of AoA/ZoA in LCS
• Distribution of AoA measurement error for an NLOS/LOS link
• Other Details (e.g., mean, standard deviation)

Note: It is encouraged to provide evaluation assumptions (e.g., requirements in TS 38.101, TS 38.104, TS 38.133, evaluation assumptions in TR 38.857, LOS/NLOS probability, measurement algorithm) and results (e.g., error histogram) if evaluation is used to determine the distribution, mean and standard deviation or range of values of an error source.

9.5.2.2       Improved accuracy based on NR carrier phase measurement

R1-2205870         Evaluation and solutions for NR carrier phase positioning        Huawei, HiSilicon

R1-2205903         Discussion on carrier phase measurement based positioning     ZTE

R1-2206048         Discussion on carrier phase measurement enhancements          vivo

R1-2206227         Solutions for Integer Ambiguity, TRP synchronization and Vertical Positioning                Locaila

R1-2206274         Discussions on Carrier Phase Measurement for NR Positioning              OPPO

R1-2206407         Discussion on improved accuracy based on NR carrier phase measurement               CATT

R1-2206491         Views on improved accuracy based on NR carrier phase measurement  Nokia, Nokia Shanghai Bell

R1-2206500         On NR carrier phase measurements Lenovo

R1-2206590         Improved positioning accuracy with NR carrier phase measurements     Intel Corporation

R1-2206651         Improved accuracy based on NR carrier phase measurement    Xiaomi

R1-2206694         Discussion on improved accuracy based on NR carrier phase measurement               China Telecom

R1-2206919         Discussion on carrier phase positioning         CMCC

R1-2207090         Discussion on positioning based on NR carrier phase measurement        InterDigital, Inc.

R1-2207126         NR carrier phase measurements for positioning          Fraunhofer IIS, Fraunhofer HHI

R1-2207240         Phase Measurements in NR Positioning        Qualcomm Incorporated

R1-2207285         Views on improved accuracy based on NR carrier phase measurement  Sharp

R1-2207413         Discussion on improved accuracy based on NR carrier phase measurement          NTT DOCOMO, INC.

R1-2207480         On carrier phase measurement        MediaTek Inc.

R1-2207622         Improved accuracy based on NR carrier phase measurement    Ericsson

R1-2207710         Discussion on OFDM based carrier phase measurement in NR LG Electronics    (rev of R1-2207360)

R1-2207742         Discussion on NR Carrier Phase Measurement            Samsung              (rev of R1-2206833)

R1-2207690        FL Summary for improved accuracy based on NR carrier phase measurements               Moderator (CATT)

From Tuesday session

Agreement

Endorse the templates in section 17 under (H)(Round 1) Proposal 17-1 in R1-2207690 to collect carrier-phase based positioning simulation results, with the following notes:

• The TR editor can adjust the sections/sub-sections arrangement
• Adjust the titles of the tables to refer to NR carrier-phase based positioning
• The detailed rows of the tables can be further discussed

R1-2207691        FL Summary #2 for improved accuracy based on NR carrier phase measurements    Moderator (CATT)

Agreement

In the evaluation of NR carrier phase positioning, the following frequency errors can be considered, which are modeled independently for each UE and each TRP:

·        Initial Residual CFO (is the same for one measurement instances [or multiple phase measurement instances]):

o   Ideal: 0 (UE/TRP)

o   Practical: uniform distribution within

§  [-30, +30] Hz (FR1, UE), [-100, +100] Hz (FR1, UE),

§  [-120, +120] Hz (FR2, UE), [-400, +400] Hz (FR2, UE),

§  [-10, +10] Hz (for each TRP, FR1),

§  [-40, +40] Hz (for each TRP, FR2).

·        Oscillator-drift (is the same for one or multiple phase measurement instances for positioning fix):

o   Ideal: 0 (UE/TRP)

o   Practical: uniform distribution within [-0.1, 0.1] ppm (UE), [-0.02, +0.02] ppm (each TRP) within measurement duration

·        Note: The Doppler frequency can be determined based on the UE speed in the evaluation assumption.

Agreement

In the evaluation of NR carrier phase positioning, the offset between the initial phase of the transmitter and the initial phase of the receiver can be modeled as a random variable uniformly distributed within [0, X].

•  Possible values of X: 2pi
• Other values FFS

Agreement

In the evaluation of NR carrier phase positioning, the antenna reference point (ARP) location error of a TRP can be modeled as follows:

·        Ideal: no ARP error

·        Practical: a zero-mean, truncated Gaussian distribution with zero mean and standard deviation of T=[1, 5] cm truncated to 2T in each of (x, y, z) direction

R1-2208206        FL Summary #3 for improved accuracy based on NR carrier phase measurements    Moderator (CATT)

Agreement

In the evaluation of NR carrier phase positioning, the following the UE/TRP antenna phase center offset (PCO) model can be considered as the starting point:

dPCO =  a * dPhi + w

where

• a is the scale factor, a=[0, 1, 3]
• FFS: other values
• dPhi is the direction difference (in degrees):
• Example 1, dPhi is the difference between the true and the calculated (or measured) directions between a transmitter (UE/TRP) and a receiver (TRP/UE).
• Example 2: dPhi is the direction difference between one UE to two TRPs, or between one TRP to two UEs.
• w is 0 or a random variable uniformly distributed within [-2, +2], or [-5, +5], or [-X, +X] degrees
• FFS: value of X or left up to companies
• Note: the above model is valid only when absolute value of dPhi < Y degrees
• FFS: value of Y or left up to companies

Agreement

For the evaluation of NR carrier phase positioning, UE position can be calculated by the use of the carrier phase measurements obtained at the M sequential time instances, where

• Baseline:
• M=1
• Optional :
• M=4
• Other values of M
• Companies should report their assumptions on UE mobility (e.g. speed)

Agreement

Further evaluate the following multipath mitigation methods for the carrier phase positioning, which include, but are not limited to, the following:

• The methods of estimating the carrier phase of the first path
• Note: Both time-domain and frequency-domain methods can be considered
• LOS/NLOS/ Multi-path indication for the carrier phase measurements for improving the accuracy of the position calculation
• Rel-17 LOS/NLOS indicator can be used as the starting point
• measurements of the first path and additional paths
• E.g. carrier phase measurements, timing measurements
• other channel information, such as RSRP/RSRPP, CIR/CFR, etc.

9.5.2.3       LPHAP (Low Power High Accuracy Positioning)

Including discussions on requirements, evaluations, and potential enhancements.

R1-2205871         Evaluation and solutions for LPHAP             Huawei, HiSilicon

R1-2205904         Discussion on low power high accuracy positioning   ZTE

R1-2205996         Discussion on evaluation on LPHAP             Spreadtrum Communications

R1-2206049         Discussion on Low Power High Accuracy Positioning              vivo

R1-2206275         Disucssion on Low Power High Accuracy Positioning              OPPO

R1-2206408         Discussion on Low Power High Accuracy Positioning              CATT

R1-2206492         Views on LPHAP               Nokia, Nokia Shanghai Bell

R1-2206501         LPHAP considerations      Lenovo

R1-2206591         Discussion on power saving evaluation and techniques for LPHAP        Intel Corporation

R1-2206652         Discussion on Low Power High Accuracy Positioning              Xiaomi

R1-2206834         Discussion on LPHAP       Samsung

R1-2206920         Discussion on low power high accuracy positioning   CMCC

R1-2206921         Summary for low power high accuracy positioning    Moderator (CMCC)

R1-2207091         Discussions on Low Power High Accuracy Positioning (LPHAP) techniques               InterDigital, Inc.

R1-2207241         Requirements, Evaluations, Potential Enhancements for Low Power High Accuracy Positioning          Qualcomm Incorporated

R1-2207286         Views on low power high accuracy positioning           Sharp

R1-2207361         Discussion on LPHAP in idle/inactive state  LG Electronics

R1-2207414         Discussion on Low Power High Accuracy Positioning              NTT DOCOMO, INC.

R1-2207623         Evaluations for Low Power High Accuracy Positioning            Ericsson

R1-2206921        Summary for low power high accuracy positioning              Moderator (CMCC)

From Tuesday session

Agreement

In the LPHAP evaluation, adopt the following model to convert the relative power unit to the battery life:

·        Alt. 1: battery life is used as the metric to identify the gap

o   K is an implementation factor, K = 1 (baseline); K = 0.5, 2, 4 (optional)

·        Note: The definition of the notations will be captured in the updates of TR.

·        Note: The voltage is assumed to be the same for the reference device and the LPHAP device.

Agreement

·        In the LPHAP evaluation, adopt the following example parameter values in the conversion model to evaluate the battery life:

o   For the reference device in the conversion model:

o   For the LPHAP device, consider 2 types in the conversion model:

·        Note: As the reference device and LPHAP device characteristics, and therefore the parameter values of the model for determining battery life, is dependent on implementation factors, manufacturer, design options and cost options, it is up to individual company to evaluate the optional K values, and report the corresponding parameter values.

Agreement

In the LPHAP evaluation, adopt the example value of relative power unit of the reference device P1 = 50 to further align the battery life among companies.

Agreement

For the purpose of LPHAP evaluation, an ultra-deep sleep state is considered. The following options of the power consumption model of the ultra-deep sleep state can be further discussed:

·        Option 1:

o   The relative power unit: 0.015

o   Additional transition energy: 2000

o   Total transition time: 400ms

·        Option 2:

o   The relative power unit: 0.01

o   Additional transition energy: 450;

o   Total transition time: 25ms

o   FFS: restrictions in processing associated with option 2 after the UE comes out of ultra-deep sleep state

·        Notes: the values above can be further discussed

Agreement

For option 1 in the agreement above, the value of additional transition energy is changed to “a value between 2000 and 20000”. FFS which value.

Agreement

·        For the purpose of LPHAP evaluation, the following assumptions on eDRX configuration and/or paging reception can be optionally considered:

o   The eDRX cycle to evaluate: 20.48s; 30.72s;

o   For paging reception:

§  1 paging occasion is included in one eDRX cycle

§  10% paging rate

o   No paging reception can be optionally evaluated;

o   1 DL PRS and/or UL SRS for positioning occasion per 1 eDRX cycle

§  Minimizing the gap between PRS measurement, SRS transmission and/or measurement reporting with paging monitoring in time domain can be evaluated.

R1-2207993        Summary for low power high accuracy positioning              Moderator (CMCC)

Agreement

The tables to collect evaluation results from each source in section 3.3.2 of R1-2207993 are endorsed.

Agreement

Capture the following in TR as an observation:

·        Evaluations of baseline Rel-17 RRC_INACTIVE state positioning with the evaluation assumptions agreed for the study show that the power consumption on deep sleep state accounts for the highest proportion in the total power.

Final summary in R1-2207994.

9.5.33        Positioning for RedCap UEs

Including performance evaluation of existing positioning procedures and measurements with RedCap UEs. The result of the evaluation will be used to assess the necessity of enhancements and, if needed, identify enhancements.

R1-2205872         Discussion on RedCap positioning  Huawei, HiSilicon

R1-2205905         Discussion on Positioning for RedCap UE    ZTE

R1-2206050         Discussion on positioning for RedCap UEs   vivo

R1-2206126         Discussion on positioning for RedCap UEs   Sony

R1-2206276         Discussion on Positioning for RedCap Ues   OPPO

R1-2206426         Discussion on positioning for RedCap UEs   CATT

R1-2206473         Discussion on positioning support for RedCap UEs    NEC

R1-2206493         Views on Positioning for RedCap UEs          Nokia, Nokia Shanghai Bell

R1-2206502         Positioning for RedCap devices      Lenovo

R1-2206592         Positioning for RedCap UEs            Intel Corporation

R1-2206835         Discussion on Positioning for RedCap UEs  Samsung

R1-2206922         Discussion on RedCap positioning  CMCC

R1-2207092         Discussions on positioning for RedCap UEs InterDigital, Inc.

R1-2207242         Positioning for Reduced Capabilities UEs     Qualcomm Incorporated

R1-2207287         Views on positioning for RedCap Ues           Sharp

R1-2207342         Discussions on Positioning for RedCap Ues Apple

R1-2207362         Discussion on positioning support for RedCap Ues     LG Electronics

R1-2207415         Discussion on positioning for RedCap UEs   NTT DOCOMO, INC.

R1-2207482         The potential solutions for RedCap UEs for positioning            MediaTek Inc.

R1-2207624         Considerations for RedCap Positioning         Ericsson

R1-2207749        Feature Lead Summary #1 for Positioning for RedCap UEs              Moderator (Ericsson)

From Wed session

Agreement

For the purpose of the Rel-18 study

·        The target accuracy requirements for RedCap UEs for commercial use cases are defined as follows:

o   Indoor and outdoor

§  Horizontal position accuracy (< 3 m) for 90% of UEs

§  Vertical position accuracy (< 3 m) for 90% of UEs

·        The target accuracy requirements for RedCap UEs for IIoT use cases are defined as follows:

o   Horizontal position accuracy (<1 m) for 90% of UEs

o   Vertical position accuracy (< 3 m) for 90% of UEs 

·        Note: the requirements may not be met in all scenarios and use cases

Agreement

CDF values for evaluations of Redcap UE Positioning scenarios are derived based on:

• The reported CDF points used as performance metrics in the evaluation include at least the 50%, 67%, 80%, 90% percentiles.
• For indoor scenarios
• (Required): The UEs inside the convex hull of the horizontal BS deployment area.
• (Optional): All the UEs

Agreement

The following table is endorsed to capture the evaluation scenarios and parameters in the evaluation results section of the TR:

Table 3.2-2 evaluation scenarios and parameters template

Agreement

Endorse the templates in section 7 in R1-2207749 to collect RedCap UE positioning simulation results, with the following notes:

• The first table as endorsed in previous agreement
• Add a column to the second table for capturing whether the requirement is met or not met
• The TR editor can adjust the sections/sub-sections arrangement
• Adjust the titles of the tables to refer to RedCap UE positioning

Agreement

For the evaluation of redcap UEs in the RMa scenarios, companies should report their evaluations parameters with their results.

Agreement

The potential benefits and performance gains of frequency hopping of the DL PRS and UL SRS can be investigated in release 18, which may take into account at least the following:

·        The impact of Doppler, phase offset, timing offset, power imbalance among hops

·        RedCap UE capability and complexity considerations

·        Impact of RF retuning during frequency hopping

·        Details of frequency hopping (including Tx hopping and/or Rx hopping, BWP switching) for the study are FFS

 RAN1#110-bis-e

9.5       Study on expanded and improved NR positioning

Please refer to RP-222616 for detailed scope of the SI.

R1-2210692        Session notes for 9.5 (Study on expanded and improved NR positioning)       Ad-Hoc Chair (Huawei)

R1-2210037         Work Plan for Study Item on Expanded and Improved NR Positioning  Intel Corporation, CATT, Ericsson

R1-2210233         Draft TR 38.859 v020: Study on expanded and improved NR positioning               Intel, CATT, Ericsson

R1-2210672         Draft TR 38.859 v020: Study on expanded and improved NR positioning               Intel, CATT, Ericsson

[post-110bis-e-02] R18 Positioning TR update by Oct 24 - Debdeep (Intel)

9.5.1        Sidelink positioning

/To be handled using NWM – please use 110bis-e-NWM-R18-Pos-01 as the document name

R1-2208338        LS on Terminology Alignment for Ranging/Sidelink Positioning      SA2, Xiaomi

[110bis-e-R18-Pos-01] – Qun Zhao (Xiaomi)

Email discussion on incoming SA2 LS in R1-2208338 by October 14

R1-2210443        Moderator summary on discussion on incoming SA2 LS in R1-2208338 on terminology alignment    Moderator (Xiaomi)

R1-2210550        [Draft] Reply LS on Terminology Alignment for Ranging/Sidelink Positioning               Xiaomi

Decision: As per email decision posted on Oct 15th, the draft reply LS is endorsed. Final version is approved in R1-2210567.

9.5.1.1       Evaluation of SL positioning

Including evaluation methodology and performance evaluation results

R1-2208363         Evaluation of SL positioning           Nokia, Nokia Shanghai Bell

R1-2208452         SL positioning evaluations Huawei, HiSilicon

R1-2208647         Evaluation of sidelink positioning performance           vivo

R1-2208820         Evaluation methodology and results of SL positioning              OPPO

R1-2208980         Evaluation methodology and performance evaluation for SL positioning               CATT, GOHIGH

R1-2209104         Discussion on evaluation of SL positioning  Sony

R1-2209212         Discussion on evaluation of SL positioning  ZTE, CMCC

R1-2209290         Discussion on evaluation of sidelink positioning         xiaomi

R1-2209392         SL Positioning Evaluation and Performance Lenovo

R1-2209482         Discussion on evaluation of SL positioning  LG Electronics

R1-2209486         Evaluation results for SL positioning             InterDigital, Inc.

R1-2209735         Discussion on Evaluation for SL Positioning Samsung

R1-2209782         SL positioning scenarios   Sharp

R1-2209989         Sidelink Positioning Evaluation Assumptions and Results        Qualcomm Incorporated

R1-2210038         Evaluation of SL positioning           Intel Corporation

R1-2210111         Evaluation results and observations on V2X and IIoT use case for sidelink positioning           CEWiT

R1-2210174         Evaluation of NR SL positioning and ranging             Ericsson

[110bis-e-R18-Pos-02] – Chuangxin (ZTE)

Email discussion on evaluation of SL positioning by October 19

-        Check points: October 14, October 19

R1-2209459        Summary #1 for SL positioning evaluation              Moderator (ZTE)

From Oct 10th GTW session

Observation

The performance analysis for Rel-18 SL positioning shows that, with increasing of bandwidth of SL PRS, the positioning accuracy improves for both absolute positioning and relative positioning/ranging for all evaluated scenarios.

Observation

The performance analysis for Rel-18 SL positioning shows that different SL positioning methods can be used to determine absolute position of a target UE: 

·        Simulation results based SL-TDOA were provided in contributions from 10 sources ([Nokia 1], [OPPO 4], [CATT, GOHIGH 5], [Sony 6], [ZTE,CMCC 7], [Lenovo 9], [LG 10], [InterDigital 11], [Intel 15], [CEWiT 16])

·        Simulation results based on SL-RTT (multi-RTT) were provided in contributions from 6 sources ([Huawei 2], [vivo 3], [LG 10], [InterDigital 11], [Qualcomm 14], [Samsung 12])

·        Simulation results based on two anchors SL-AOA and single anchor SL-TOA+AOA were provided in contribution from 1 source ( [Lenovo 9])

Note: at least the number of sources and the references can be further updated in next meeting depending on companies’ update of simulation results.

Decision: As per email decision posted on Oct 15th,

Observation

The performance analysis for Rel-18 SL positioning shows that, SL positioning methods can be used for relative positioning/ ranging between UEs. For relative positioning/ranging positioning accuracy,

• Simulation results based SL-RTT and/or AOA were provided in contributions from 10 sources ([Huawei 2], [vivo 4], [CATT, GOHIGH 5], [Sony 6], [ZTE, CMCC 7], [Xiaomi 8], [Lenovo 9], [LG 10], [Qualcomm 14], [Intel 15] )
• Results based SL-TDOA were provided in contribution from 1 source ([CEWiT 16])

Note: at least the number of sources and the references can be further updated in next meeting depending on companies’ update of simulation results. 

R1-2209460         Summary #2 for SL positioning evaluation   Moderator (ZTE)

R1-2210579        Summary #3 for SL positioning evaluation   Moderator (ZTE)

From Oct 17th GTW session

Observation

For V2X use case in highway scenario, 13 sources ([Huawei 2], [vivo 3], [OPPO 4], [CATT,GOHIGH 5], [Sony 6], [ZTE,CMCC 7], [Lenovo 9], [LG 10], [Samsung 12], [Qualcomm 14], [Intel 15], [CEWiT 16], [Ericsson 17]) provide simulation results for FR1, and 1 source ([CEWiT 16]) provides simulation results for FR2.

• For absolute horizontal accuracy, the results were provided by 13 sources. 11 out of 13 sources show that, the target requirement set A can be achieved, and 9 out of 13 sources show that the target requirement set B cannot be achievable even by 100MHz.
• The requirement 1.5m@90% (Set A)
• is achieved with 20MHz bandwidth in contributions from 3 sources ([ZTE,CMCC 7], [Lenovo 9], [CEWiT 16]),
• where SL ToA+AoA technique and optional antenna configuration is used in contribution from ([Lenovo 9])
• and is achieved with at least 40MHz bandwidth in contributions from 4 sources ([Huawei 2], [CATT,GOHIGH 5], [LG 10], [Samsung 12]),
• and is achieved with at least 100MHz bandwidth in contributions from 5 sources ([vivo 3], [OPPO 4], [Sony 6], [Lenovo 9], [Ericsson 17]),
• where SL-TDOA technique is used in contribution from ([Lenovo 9])
• and is NOT achieved with 100MHz bandwidth in contributions from 2 sources ([Qualcomm 14], [Intel 15])
• The requirement 0.5m@90% (Set B)
• is achieved with 40MHz in contribution from 1 source ([Samsung 12]),
• and is achieved with at least100MHz in contributions from 3 sources ([Huawei 2], [CATT,GOHIGH 5], [ZTE,CMCC 7]),
• where Joint Uu/SL positioning is used in contribution from ([ZTE,CMCC 7])
• and is NOT achieved with100MHz bandwidth in FR1 or 400MHz in FR2 in contributions from 9 sources ([vivo 3], [OPPO 4], [Sony 6], [ZTE,CMCC 7], [Lenovo 9], [Qualcomm 14], [Intel 15], [CEWiT 16], [Ericsson 17]),
• where SL-only positioning is used in contribution from ([ZTE,CMCC 7])
• For absolute vertical accuracy, the results were provided by 1 source out of 13 sources.
• The requirement 3m@90% (Set A)
• is achieved with at least 100MHz bandwidth in contribution from 1 source ([ZTE,CMCC 7])
• The requirement 2m@90% (Set B)
• is achieved with 100MHz bandwidth in contribution from 1 source ([ZTE,CMCC 7])
• For relative horizontal accuracy, the results were provided by 5 sources out of 13 sources. The performance of relative horizontal accuracy is worse than that of distance accuracy of ranging mainly due to additional angle estimation error. All 5 sources show Set B cannot be met even by 100MHz in the case without RSU-UE positioning.
• The requirement 1.5m@90% (Set A)
• is achieved with at least 40MHz bandwidth in contributions from 2 sources ([Huawei 2], [CATT,GOHIGH 5])
• X = 20m in contribution from ([CATT,GOHIGH 5])
• X = 50m in contribution from ([Huawei 2]) where RSU deployment is additionally used for performing relative positioning
• and is achieved with at least 100MHz bandwidth in contributions from 3 source ([Huawei 2], [CATT,GOHIGH 5], [CEWiT 16])
• X = 25m in contribution from ([CATT,GOHIGH 5])
• X = 150m in contributions from ([Huawei 2], [CEWiT 16]), where BS or RSU deployment is additionally used for performing relative positioning
• and is NOT achieved with 100MHz bandwidth in contributions from 4 sources ([Huawei 2], [vivo 3], [CATT,GOHIGH 5], [Sony 6])
• X = 100m and 150m in contribution from ([CATT,GOHIGH 5])
• X = 25m, 50m, and 100m in contribution from ([vivo 3])
• X = 50m in contribution from ([Sony 6])
• X = 50m and 150m in contribution from ([Huawei 2])
• The requirement 0.5m@90% (Set B)
• is achieved with at least 100MHz bandwidth in contributions from 1 source ([Huawei 2])
• X = 50m in contribution from ([Huawei 2]) where RSU deployment is additionally used for performing relative positioning
• is NOT achieved with 100MHz bandwidth in FR1 or 400MHz in FR2 in contributions from 5 sources ([Huawei 2], [vivo 3], [CATT,GOHIGH 5], [Sony 6], [CEWiT 16])
• For distance accuracy of ranging, the results were provided by 9 out of 13 sources. 5 of 9 sources show that the target requirement set A can be achievable by 20MHz, and 5 out of 9 sources show that the target requirement set B can be achievable by larger bandwidth, e.g. 40MHz or 100MHz, and 3 of 9 sources show that the target requirement set B cannot be achieved with 100MHz bandwidth.
• The requirement 1.5m@90% (Set A)
• is achieved with 20MHz bandwidth in contributions from 5 sources ([Huawei 2], [vivo 3], [CATT,GOHIGH 5], [ZTE,CMCC 7], [CEWiT 16])
• X = 50m and 150 in contribution from ([Huawei 2])
• X = 20m, 25m, 100m and 150m in contribution from ([CATT,GOHIGH 5])
• X = 25m, 50m, and 100m in contribution from ([vivo 3])
• X = 150m in contribution from ([CEWiT 16]), where RSU deployment is additionally used for performing distance ranging
• X = 100m, 200m and 300m in contribution from ([ZTE,CMCC 7])
• and is achieved with at least 40MHz bandwidth in contribution from 1 source ([LG 10])
• X = 80m and 160m in contribution from ([LG 10])
• and is achieved with at least 100MHz bandwidth in contributions from 4 sources ([Sony 6], [Lenovo 9], [Qualcomm 14], [Intel 15])
• X = 50m in contribution from ([Sony 6])
• X = 50m and 100m in contribution from ([Lenovo 9], [Intel 15])
• X = 100 m in contribution from ([Qualcomm 14])
• The requirement 0.5m@90% (Set B)
• is achieved with at least 40MHz in contributions from 3 sources ([Huawei 2], [vivo 3], [CEWiT 16])
• X = 50m in contribution from ([Huawei 2])
• X = 25m, 50m, and 100m in contribution from ([vivo 3])
• X = 150m in contribution from ([CEWiT 16]), where RSU deployment is additionally used for performing distance ranging
• and is achieved with at least 100MHz in contributions from 4 sources ([Sony 6], [Huawei 2], [CATT,GOHIGH 5], [ZTE,CMCC 7])
• X = 150m in contribution from ([Huawei 2])
• X = 25m, 100m and 150m in contribution from ([CATT,GOHIGH 5])
• X = 50m in contribution from ([Sony 6])
• X = 100m in contribution from ([ZTE,CMCC 7]
• and is NOT achieved with 100MHz bandwidth in contributions from 3 sources ([Lenovo 9], [Qualcomm 14], [Intel 15])
• X = 50m and 100m in contribution from ([Lenovo 9], [Intel 15])
• X = 100 m in contribution from ([Qualcomm 14])
• For angle accuracy of ranging, the results were provided by 6 sources out of 13 sources. All 6 sources show that both the target requirement set A and set B can be achieved by 20MHz or 40MHz.
• The requirement 15°@90% (Set A)
• is achieved with 20MHz bandwidth in contributions from 5 sources ([Huawei 2], [vivo 3] ,[CATT,GOHIGH 5], [Sony 6], [Lenovo 9]),
• and is achieved with 40MHz bandwidth in contribution from 1 source ([ZTE,CMCC 7])
• The requirement 8°@90% (Set B)
• is achieved with 20MHz in contributions from 3 sources ([Huawei 2], [Sony 6], [Lenovo 9]),
• and is achieved with at least 40MHz in contributions from 3 sources ([vivo 3], [CATT,GOHIGH 5], [ZTE,CMCC 7])
• Note: the above observations can be further updated in next meeting depending on companies’ new/update of simulation results, including editorial modifications, X values, replacing sources by references, additional sources and other revisions.
• Note: for each SL PRS bandwidth, the above observations are based on the best performance from each source.
• Note: for the relative positioning accuracy or distance accuracy of ranging, X is the maximum distance between UEs for performing relative positioning or ranging.
• Note: a list of the sources that used super resolution in the evaluations will be captured in the observations in next meeting.

Observation

For V2X use case in Urban grid scenario, 10 sources ([Huawei 2], [vivo 3], [OPPO, 4], [CATT,GOHIGH 5], [Sony 6],  [ZTE,CMCC 7], [xiaomi 8], [Lenovo 9], [Intel 15], [CEWiT 16]) provide simulation results for FR1, and 1 source ([CEWiT 16]) provide simulation results for FR2.

• For absolute horizontal accuracy, the results were provided by 8 out of 13 sources. 5 out of 8 sources show that target requirements set A cannot be achieved, and 7 out of 8 sources show that target requirements set B cannot be achieved.
• The requirement 1.5m@90% (Set A)
• is achieved with 20MHz in contributions from 2 sources ([Lenovo 9], [CEWiT 16]),
• where SL ToA+AoA technique and optional antenna configuration is used in contribution from ([Lenovo 9])
• and is achieved with at least100MHz in contribution from 1 source ([ZTE,CMCC 7]),
• and is NOT achieved with 100MHz bandwidth in contributions from 5 sources ([Huawei 2], [vivo 3], [OPPO, 4], [CATT,GOHIGH 5], [Intel 15])
• The requirement 0.5m@90% (Set B)
• is achieved with at least 100MHz in contribution from 1 source ([ZTE,CMCC 7]),
• and is NOT achieved with 100MHz bandwidth in FR1 or 400MHz in FR2 in contributions from 7 sources ([Huawei 2], [vivo 3], [OPPO 4], [CATT,GOHIGH 5], [Lenovo 9], [Intel 15], [CEWiT 16])
• For Relative horizontal accuracy, the results were provided by 5 out of 13 sources. The performance of relative horizontal accuracy is worse than that of distance accuracy of ranging mainly due to additional angle estimation error. All 5 sources show that the target requirement set B is not achieved even by 100MHz. 3 sources show that the target requirement Set A can be achieved by 40MHz or 100MHz in case of X=10m.
• The requirement 1.5m@90% (Set A)
• is achieved with at least 40MHz bandwidth  in contributions from 1 sources ([vivo 3])
• only for the case of X = 10m and the relative positioning is performed with LOS link only in contribution from ([vivo 3])
• and is achieved with at least100MHz bandwidth  in contributions from 2 sources ([Huawei 2], [CATT,GOHIGH 5])
• X = 10m in contributions from ([Huawei 2], [CATT,GOHIGH 5])
• and is NOT achieved with 100MHz bandwidth in contributions from 5 sources ([vivo 3], [Huawei 2], [CATT,GOHIGH 5], [Sony 6], [CEWiT 16])
• X = 50m in contribution from ([Huawei 2])
• X = 25m in contribution from ([CATT,GOHIGH 5])
• X = 30m in contribution from ([Sony 6])
• X = 10m, 25m, and 50m in contribution from ([vivo 3])
• The requirement 0.5m@90% (Set B)
• is NOT achieved  with 100MHz bandwidth in FR1 or 400MHz in FR2 in contributions from 5 sources ([Huawei 2], [vivo 3], [CATT,GOHIGH 5], [Sony 6], [CEWiT 16])
• For distance accuracy of ranging, the results were provided by 9 out of 13 sources. Based on the results by a majority of sources, target requirements set A may be achievable by smaller bandwidth, e.g. 20MHz or 40MHz, and set B may be achieved by larger bandwidth, e.g. 100MHz or may even not be achievable.
• The requirement 1.5m@90% (Set A)
• is achieved with at least 20MHz in contributions from 3 sources ([vivo 3], [CATT,GOHIGH 5],, [CEWiT 16])
• X = 25m in the case when the relative positioning is performed with all links, X = 25m, 50m, and 100m in the case when the relative positioning is performed with LOS link only in contribution from ([vivo 3])
• X = 10m and 25m in contribution from ([CATT,GOHIGH 5])
• X = 150m in contribution from ([CEWiT 16]) where RSU deployment is additionally used for performing distance ranging
• and is achieved with at least 40MHz in contributions from 2 sources ([ZTE,CMCC 7], [xiaomi 8])
• X = 20m and 30m in contribution from ([ZTE,CMCC 7])
• X = 20m, 50m and 100m in contribution from ([xiaomi 8])
• and is achieved with at least 100MHz in contributions from 1 source ([Huawei 2])
• X = 10 and 50m in contribution from ([Huawei 2])
• and is NOT achieved with 100MHz bandwidth  in contributions from 4 sources ([vivo 3], [Sony 6], [Lenovo 9], [Intel 15])
• X = 50m and 100m in contribution from ([vivo 3])
• X = 30m in contribution from ([Sony 6])
• X = 50m, 100m in contribution from ([Lenovo 9], [Intel 15])
• The requirement 0.5m@90% (Set B)
• is achieved with at least 40MHz in contributions from 1 source ([vivo 3])
• X = 25m, 50m, 100m in the case when the relative positioning is performed only with LOS links in contribution from ([vivo 3])
• and is achieved with at least 100MHz in contributions from 3 sources ([Huawei 2], [CATT,GOHIGH 5], [xiaomi 8])
• X = 10m and 50m in contribution from ([Huawei 2])
• X = 10m and 25m in contribution from ([CATT,GOHIGH 5]
• X = 20m, 50m, 100m in contribution from ([xiaomi 8])
• and is NOT achieved with 100MHz bandwidth in FR1 or 400MHz in FR2  in contributions from 6 sources ([vivo 3], [Sony 6], [ZTE,CMCC 7], [Lenovo 9], [Intel 15], [CEWiT 16])
•  where the relative positioning is performed with all links in contribution from ([vivo 3])
• For angle accuracy of ranging, the results were provided by 5 out of 13 sources.
• The requirement 15°@90% (Set A)
• is achieved with 20MHz in contribution from 2 sources ([Lenovo 9], [Huawei 2])
• and is achieved with at least 100MHz in contribution from 1 source [CATT,GOHIGH 5]
• and is NOT achieved with 100MHz bandwidth in contributions from 2 sources ([vivo 3], [Sony 6])
• The requirement 8°@90% (Set B)
• is achieved with 20MHz in contribution from 1 source ([Lenovo 9])
• and is achieved with at least 40MHz in contribution from 1 source ([Huawei 2])
• and is NOT achieved with 100MHz bandwidth in contributions from 3 sources ([vivo 3], [CATT,GOHIGH 5], [Sony 6])
• Note: the above observations can be further updated in next meeting depending on companies’ new/update of simulation results, including editorial modifications, X values, replacing sources by references, additional sources and other revisions.
• Note: for each SL PRS bandwidth, the above observations are based on the best performance from each source.
• Note: for the relative positioning accuracy or distance accuracy of ranging, X is the maximum distance between UEs for performing relative positioning or ranging.
• Note: a list of the sources that used super resolution in the evaluations will be captured in the observations in next meeting.

Observation

Simulation results in contributions from 7 sources ([Huawei 2], [vivo 3], [CATT,GOHIGH 5], [ZTE,CMCC 7], [xiaomi 8], [LG 10], [Intel 15]) show that relative horizontal accuracy and/or distance accuracy of ranging performance improves with X value decreasing, where X is the maximum distance between two UEs for performing relative positioning or ranging.  

• In some simulation cases, a target requirement may be achieved in condition of a smaller X value but not be achieved in condition of a larger X value for a certain SL PRS bandwidth.
• In some simulation cases, a target requirement may be achieved in condition of a smaller X value and a smaller SL PRS bandwidth, but can be achieved in condition of a larger X value and a larger SL PRS bandwidth.

Note: the above observations can be further updated in next meeting depending on companies’ new/update of simulation results, including editorial modifications, X values, replacing sources by references, additional sources and other revisions.

9.5.1.2       Potential solutions for SL positioning

R1-2208364         Potential solutions for SL positioning            Nokia, Nokia Shanghai Bell

R1-2208372         Potential solutions for sidelink positioning   FUTUREWEI

R1-2208453         Discussion on SL positioning solutions         Huawei, HiSilicon

R1-2208558         Discussion on potential solutions for SL positioning  Spreadtrum Communications

R1-2208648         Discussion on potential solutions for sidelink positioning         vivo

R1-2208773         Discussion on potential solutions for sidelink positioning         China Telecom

R1-2208821         Discussion on potential solutions for SL positioning  OPPO

R1-2208981         Discussion on potential solutions for SL positioning  CATT, GOHIGH

R1-2209058         Potential solutions for SL positioning            Intel Corporation

R1-2209105         Consideration on potential solutions for SL positioning            Sony

R1-2209151         Discussion on potential solutions for SL positioning  NEC

R1-2209213         Discussion on potential solutions for SL positioning  ZTE

R1-2209291         Discussion on sidelink positioning solutions xiaomi

R1-2209341         Discussion on potential solutions for SL positioning  CMCC

R1-2209393         Potential SL Positioning Solutions  Lenovo

R1-2209483         Discussion on potential solutions for SL positioning  LG Electronics

R1-2209487         Potential solutions for SL positioning            InterDigital, Inc.

R1-2209533         Potential solutions for SL positioning            Faunhofer IIS, Fraunhofer HHI

R1-2209589         Discussions on Potential solutions for SL positioning Apple

R1-2209675         Discussion on potential solutions for SL positioning  DENSO CORPORATION

R1-2209736         Discussion on Potential Solutions for SL Positioning Samsung

R1-2209783         Views on potential solutions for SL positioning          Sharp

R1-2209797         Discussion on sidelink positioning  ASUSTeK

R1-2209907         Discussion on potential solutions for SL positioning  NTT DOCOMO, INC.

R1-2209990         Potential Solutions for Sidelink Positioning  Qualcomm Incorporated

R1-2210097         The potential solutions for sidelink positioning           MediaTek Inc.

R1-2210102         Considerable solutions on sidelink positioning in NR ITL

R1-2210112         Discussion on enhancements for sidelink based positioning      CEWiT

R1-2210175         On potential solutions for SL positioning      Ericsson

[110bis-e-R18-Pos-03] – Alex (Qualcomm)

Email discussion on potential solutions for SL positioning by October 19

-        Check points: October 14, October 19

R1-2210341        Moderator Summary #1 on potential solutions for SL positioning    Moderator (Qualcomm Incorporated)

From Oct 10th GTW session

Agreement

• With regards to the RTT-type solutions using SL, down-select between the following 2 alternatives:
• Alt. 1: it corresponds to a single-sided RTT method
• Alt. 2: it may correspond to either a single-sided or double-sided RTT method
• With regards to the double-sided RTT,
• companies are encouraged to analyze and evaluate the effect in performance for the single-sided SL RTT due to clock drift
• Study the order of the SL-PRS transmissions for double-sided RTT
• Study the impact of UE mobility
• FFS study whether there is or what is the spec impact of double-sided RTT method
• Note: the above may correspond to RTT with one or multiple devices

Agreement

For the study of SL-AoA positioning method,

• Both SL Azimuth of arrival (AoA) and SL zenith of arrival (ZoA) measurement should be included
• FFS: Definition of the measurements

• Study further whether other measurements can be applicable
• Study further the frame of reference (LCS or GCS)

Agreement

With regards to SL-TDOA positioning method for SL-only positioning,

• It corresponds to a method where SL-PRS is being transmitted from multiple anchor UEs to a target UE (i.e., DL-TDOA-like operation), and/or from a target UE to multiple anchor UEs (i.e. UL-TDOA-like operation) at least for the purpose of absolute positioning estimation of the target UE
• Study the detailed procedure, necessary signalling for SL-TDOA, method(s) to mitigate impact of synchronization error between multiple anchor UEs including whether such method(s) are needed.

R1-2210381        Moderator Summary #2 on potential solutions for SL positioning    Moderator (Qualcomm Incorporated)

From Oct 13th GTW session

Agreement

• From the potential candidate Positioning methods using at least SL measurements, at least the following should be introduced:
• RTT-type solution(s) using SL
• SL-AoA
• SL-TDOA
• FFS: SL-AoD

Decision: As per email decision posted on Oct 15th,

Agreement

Regarding Scheme 1 SL-PRS resource allocation, a transmitting UE receives a SL-PRS resource allocation signaling from the network. Consider one or more of the following options:

• Opt. 1: through higher layers from the LMF
• Opt. 2: through Dynamic grant, or through configured grant type 1/type 2 from gNB
• Up to further discussion which one or more of these shall be applicable

R1-2210522        Moderator Summary #3 on potential solutions for SL positioning    Moderator (Qualcomm Incorporated)

From Oct 17th GTW session

Agreement

For the sequence of the new reference signal for SL positioning/ranging, use

• Alt. 1: pseudorandom-based. Use existing sequence of DL-PRS as a starting point.

Agreement

From RAN1 perspective, the following cast types of SL-PRS transmission can be introduced for SL positioning: Unicast, Groupcast (not including many to one)

• Broadcast (as a working assumption).
• FFS: Applicability of the above cast types

R1-2210598        Moderator Summary #4 on potential solutions for SL positioning    Moderator (Qualcomm Incorporated)

From Oct 19th GTW session

Agreement

With regards to the frequency and time domain pattern of a SL-PRS resource within a slot has the following characteristics:

• With regards to the value N (comb size) and the number M of SL-PRS symbols within a slot excluding the symbol(s) used for AGC training / RxTx Turnaround:
• At least the following values are considered as potential candidate values: N = {1,2,4,6,8,12}
• FFS: the values considered as potential candidate values for M
• FFS1: Whether to consider N>12 as a potential candidate value(s)
• The symbols of a SL-PRS resource within a slot are consecutive symbols
• FFS: consecutive and/or non-consecutive symbols for shared resource pool (if supported)
• FFS: RE-Offset sequence within a SL-PRS resource, including whether to have in the end of the SL-PRS pattern a symbol with the same RE-offset as the first symbol, for phase-tracking purpose

Agreement

For a dedicated resource pool for SL positioning,

• With regards to which channels can be included in the resource pool in addition to SL-PRS, consider the following options:
• Opt. 1: No other channel can be included beyond SL-PRS
• Opt. 2: PSCCH which carries SCI associated with SL-PRS transmission(s) is included
• Opt. 3: PSCCH which carries SCI associated with SL-PRS transmission(s) and PSSCH associated with SL-PRS transmission(s) are included
• FFS: Details
• FFS: definition of PSSCH associated with SL-PRS transmission(s)
• Note: Companies are encouraged to provide their analysis and views on the above

Agreement

With regards to the SL Positioning resource allocation, for SL Positioning resource (pre-)configuration in a shared resource pool with Rel-16/17/18 sidelink communication (if supported), backward compatibility with legacy Rel-16/17 UEs should be ensured.

Agreement

With regards to SL signaling of the reservation/indication of SL-PRS resource(s) for dedicated resource pool and shared resource pool (if supported) for positioning:

• Option A.1: SCI can be used for reserving/indicating one or more SL-PRS resource(s)
• Note: This does NOT mean that only SCI is being used. There can still be higher layer signaling for the purpose of indicating a part of SL-PRS configuration.
• FFS: Whether SCI is single stage SCI or two stage SCI
• FFS: SL-MAC-CE or other higher-layer signaling reservation/indication

Decision: As per email decision posted on Oct 20th,

Agreement

With regards to the Positioning methods supported using SL-PRS measurements

• at least the following measurements are considered:

• SL Rx-Tx measurement
• SL RSTD measurement
• SL RSRP measurement
• SL RSRPP measurement
• SL RTOA measurement
• SL Azimuth of arrival (AoA) and SL zenith of arrival (ZoA) measurement

• Companies are encouraged to study other measurements (e.g., time difference of arrival of 2 SL-PRS transmitted at 2 different times from the same anchor) and provide their analysis into why they are needed in light of the above measurements.
• Companies are encouraged to study potential enhancements, such as SL Rx-Tx measurement not being reported but the transmit time of SL-PRS being adjusted based on the measurement
• FFS any additional measurements

Agreement

At least for a dedicated resource pool for positioning,

• With regards to the bandwidth of SL-PRS transmission, downselect from the following alternatives:
• Alt. 1: The bandwidth of SL-PRS can be same or smaller than that of the resource pool
• Alt. 2: The bandwidth of SL-PRS shall be the same as that of the resource pool
• Note: Companies are encouraged to provide their analysis and views on the above alternatives
• FFS: Bandwidth of SL-PRS transmission for shared resource pool (if supported)

Agreement

Study further the granularity of time-domain resource allocation for SL-PRS transmission.

Agreement

With regards to the SL-PRS time domain behavior, at least study the following behaviors from Tx UE perspective:

• Periodic SL-PRS
• SL-PRS is transmitted periodically with a transmission periodicity
• FFS: any additional details, including whether or not higher layers can start/stop transmission.
• Semi-persistent SL-PRS
• SL-PRS is transmitted periodically with a transmission periodicity after activation and until deactivation
• FFS: any additional details
• Aperiodic SL-PRS
• SL-PRS is transmitted at least once after [triggering/request]
• Note: the brackets in the above means that companies are encouraged to study further whether “triggering” and/or “request” should be used and provide their definitions.
• FFS: any additional details
• FFS: Applicability of the above time behaviors for scheme 1 & scheme 2
• FFS: Rx UE behavior is separately discussed.
• FFS: What mechanism(s) are used for activation/deactivation/triggering is part of the study

9.5.2        Improved positioning accuracy, integrity, and power efficiency

9.5.2.1       Solutions for integrity of RAT dependent positioning techniques

R1-2208454         Error source for NR RAT-dependent positioning        Huawei, HiSilicon

R1-2208480         Discussion on integrity of RAT dependent positioning              BUPT     (Withdrawn)

R1-2208516         Discussion on integrity of RAT dependent positioning              BUPT

R1-2208649         Discussion on solutions for integrity of RAT-dependent positioning      vivo

R1-2208735         Views on solutions for integrity of RAT-dependent positioning techniques               Nokia, Nokia Shanghai Bell

R1-2208800         Discussions on Integrity for NR Positioning OPPO

R1-2208982         Discussion on solutions for integrity of RAT dependent positioning techniques               CATT

R1-2209002         Discussion on error sources for RAT dependent positioning     Spreadtrum Communications

R1-2209106         Discussion on Error Sources for Integrity of NR Positioning    Sony

R1-2209214         Discussion on integrity of RAT dependent positioning              ZTE

R1-2209292         Error source for NR RAT-dependent positioning integrity        xiaomi

R1-2209342         Discussion on integrity for RAT-dependent positioning            CMCC

R1-2209394         Integrity aspects for RAT-dependent positioning        Lenovo

R1-2209488         Discussion on integrity for RAT dependent positioning techniques        InterDigital, Inc.

R1-2209737         Discussion on Integrity of RAT Dependent Positioning            Samsung

R1-2209784         Views on solutions for integrity of RAT dependent positioning techniques               Sharp

R1-2209908         Discussion on solutions for integrity of RAT dependent positioning techniques   NTT DOCOMO, INC.

R1-2209991         Integrity for RAT dependent positioning       Qualcomm Incorporated

R1-2210176         Error Sources characterization for integrity of RAT dependent positioning techniques               Ericsson

[110bis-e-R18-Pos-04] – Fumihiro (InterDigital)

Email discussion on solutions for integrity of RAT dependent positioning techniques by October 19

-        Check points: October 14, October 19

R1-2210274        FL summary #1 on integrity of RAT dependent positioning techniques               Moderator (InterDigital, Inc.)

From Oct 10th GTW session

Agreement

• The following distributions are identified as candidates for modeling of the distribution for inter-TRP synchronization error (e.g., NR-RTD-Info in TS 37.355)
• Uniform distribution
• Note: this may already be consistent with the existing parameter NR-RTD-Info in TS 37.355
• Normal distribution
• Note: it is up to RAN2 how to use the identified distributions

Agreement

• For LMF-based positioning integrity mode, TRP location (e.g., Geographical Coordinates in TS 38.455) is an error source for DL-TDOA, DL-AoD, UL-TDOA, UL-AoA and multi-RTT.
• Note : Definition of “LMF-based positioning integrity mode” can be found in Table 9.4.1.1.1 in TR 38.857
• FFS : Specification impact of TRP location as an error source for LMF-based positioning integrity mode
• FFS : Model of the error source (e.g., distribution, mean and/or standard deviation for integrity)

Agreement

• Study the following alternatives for expression of angle of arrival measurement error for determination of positioning integrity for UL-AoA, and down select between Alt 1 and Alt 2:
• Alt. 1 : No conversion (e.g., the measurement error is expressed as error in AoA or ZoA in LCS/GCS)
• Alt. 2 : conversion function ( defined function of AoA/ZoA in LCS)
• FFS : Distribution of AoA measurement error for an NLOS/LOS link
• FFS : Other Details (e.g., mean, standard deviation)

Agreement

• Timing measurement error can be modeled as Normal distribution.
• Note : The timing measurement is applicable to RSTD, RTOA and UE/gNB Rx-Tx time difference measurement
• Note: it is assumed that the timing measurement error is associated with the first path
• Note: it is up to RAN2 how to use the identified distribution

Decision: As per email decision posted on Oct 15th,

Agreement

Capture the following into the TR

• For UE-based positioning integrity mode, potential specification impacts related to errors in assistance data (e.g., to inter-TRP synchronization error and TRP locations) are at least enhancements in assistance data sent from the LMF to the UE (e.g., inclusion of parameters related to the error sources).
• Note : Definition of “UE-based positioning integrity mode” can be found in Table 9.4.1.1.1 in TR 38.857.

Agreement

• For UE-based positioning integrity mode, study whether boresight direction of DL PRS (NR-DL-PRS-BeamInfo) and/or beam information (NR-TRP-BeamAntennaInfo) of DL PRS are error sources or not, focusing on the following aspects:
• Granularity of boresight direction of DL-PRS and its influence on positioning integrity
• Feasibility and complexity of modeling
• Feasibility of obtaining quality/statistical parameters of beam information from the gNB
• Influence on measurement errors at the UE
• Other aspects are not precluded
• Note : Definition of “UE-based positioning integrity mode” can be found in Table 9.4.1.1.1 in TR 38.857.

Agreement

• From RAN1 perspective, study of the application of DNU flag for determination of positioning integrity is within the scope of RAN2 discussion.

Agreement

• The following distributions are identified as candidates for modeling of the distribution for TRP location (e.g., NR-TRP-LocationInfo in TS 37.355) error
• Uniform distribution
• Note: this may already be consistent with the uncertainty related to NR-TRP-LocationInfo specified in TS 37.355
• Normal distribution
• Note: it is up to RAN2 how to use the identified distributions

R1-2210428        FL summary #2 on integrity of RAT dependent positioning techniques               Moderator (InterDigital, Inc.)

From Oct 17th GTW session

Agreement

• In the agreement on the distribution of the timing measurement error, it is assumed that the timing measurement error contains TEG related TX/RX timing error if the TEG related information is provided.
• Note: The timing measurement is applicable to RSTD, RTOA and UE/gNB Rx-Tx time difference measurement
• Note: it is assumed that the timing measurement error is associated with the first path
• Note: no more discussion on TEG related TX/RX timing error as an independent error source from timing measurement error

Agreement

·        Study to determine whether DL PRS RSRP/RSRPP measurement is an error source for DL-AoD, focusing at least on the following aspect

·        Impact of RSRP/RSRPP measurement on positioning accuracy

·        FFS : Model of the error source (e.g., distribution, mean and/or standard deviation for integrity overbounding model, range)

Decision: As per email decision posted on Oct 20th,

Agreement

• Study to determine whether SFN initialization time is an independent error source for the following positioning methods and integrity mode
• UL-TDOA with LMF-based positioning integrity mode
• UE-assisted DL-TDOA with LMF-based positioning integrity mode
• FFS: Model of the error source (e.g., distribution, mean and/or standard deviation for integrity overbounding model, range)

·        Note: Definition of “LMF-based positioning integrity mode” can be found in Table 9.4.1.1.1 in TR 38.857

Final summary in R1-2210633.

9.5.2.2       Improved accuracy based on NR carrier phase measurement

R1-2208455         Discussion on NR carrier phase positioning  Huawei, HiSilicon

R1-2208650         Discussion on carrier phase measurement enhancements          vivo

R1-2208736         Views on improved accuracy based on NR carrier phase measurement  Nokia, Nokia Shanghai Bell

R1-2208774         Discussion on improved accuracy based on NR carrier phase measurement               China Telecom